Agent skill

Code Review Guide

by mohitagw15856 in mohitagw15856/pm-claude-skills

Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters.

MITAuto-check passedDevelopment

Install Code Review Guide

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill code-review-guide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills code-review-guide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/code-review-guide .claude/skills/code-review-guide && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
code-review-guide
GitHub stars
1.4k
Token cost
~931 tokens
SKILL.md length
449 words
Files
1
Skills in repo
1,322
Repo updated
First seen
Licence
MIT

At a glance

Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters.

  • Works in 5 steps: Correctness — does it do what it claims?… → Security & data — input validation,… → Design — is this the right approach?… → …
  • Giving PR feedback
  • SKILL.md covers Required Inputs, Output Format, Quality Checks and Anti-Patterns, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Code Review Guide is an agent skill from mohitagw15856/pm-claude-skills. Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters. Use when reviewing code, giving PR feedback, or asked to 'review this change'. Produces a structured review: a correctness/design pass, comments ranked by severity (blocking → nit), what's done well, and a clear approve / request-changes call — feedback that improves the code and the author.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code review and Pull requests. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Giving PR feedback
  • Asked to review this change

Example prompts

  • “review this change”
  • “/code-review-guide”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Correctness — does it do what it claims? Edge cases, error handling, off-by-ones, concurrency.
  2. Security & data — input validation, authz, secrets, injection, PII handling.
  3. Design — is this the right approach? Coupling, the seam, simpler alternative, future pain.
  4. Tests — do they cover the behavior and the edges? Would they catch a regression?
  5. Readability — names, clarity, dead code, docs where non-obvious.

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Review Guide loads about 931 tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 449 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~106
When it runs · the whole SKILL.md, loaded when a task matches
~931

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 449 words, ~931 tokens.

Download SKILL.mdSave it as .claude/skills/code-review-guide/SKILL.md (or your agent's skills folder).
name
code-review-guide
description
Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters. Use when reviewing code, giving PR feedback, or asked to 'review this change'. Produces a structured review: a correctness/design pass, comments ranked by severity (blocking → nit), what's done well, and a clear approve / request-changes call — feedback that improves the code and the author.

Code Review Guide Skill

Bad code review nitpicks style while missing the design flaw, or dumps 40 ungraded comments. Good review is prioritized and kind: it catches what actually matters (correctness, security, design), separates blocking issues from nits, explains the why, and leaves the author better. This skill runs that review.

Not quite this? Use code-review-checklist when you only need a checklist tailored to one change; use ai-code-review when most of the change was written by an AI assistant; use infra-as-code-review when the change is Terraform, CloudFormation or other infrastructure code.

Required Inputs

Ask for these only if they aren't already provided:

  • The change — the diff/PR, and ideally its description/intent (what it's trying to do).
  • Context — language/stack, conventions, the part of the system it touches, risk level.
  • Focus (optional) — anything specific to scrutinize (security, performance, a tricky area).

Output Format

Review: [PR / change]

Summary — in 1–2 lines: what the change does and your overall read (solid / needs work / risky).

Review passes — scan in priority order and note findings:

  1. Correctness — does it do what it claims? Edge cases, error handling, off-by-ones, concurrency.
  2. Security & data — input validation, authz, secrets, injection, PII handling.
  3. Design — is this the right approach? Coupling, the seam, simpler alternative, future pain.
  4. Tests — do they cover the behavior and the edges? Would they catch a regression?
  5. Readability — names, clarity, dead code, docs where non-obvious.

Comments (ranked by severity) — each with file/line, the issue, why it matters, and a concrete suggestion:

SeverityWhereComment & whySuggested change
🔴 Blocking
🟡 Should-fix
🔵 Nit / optional

What's done well — genuinely (specific, not flattery). Reviews are also for morale and learning.

Verdict — ✅ Approve / 🔁 Request changes / 💬 Comment — with the one or two things that gate it.

Show full SKILL.md (165 more words)Show less

Quality Checks

  • Correctness, security, and design are reviewed before style — priority order
  • Comments are ranked by severity (blocking vs. should-fix vs. nit), not a flat list
  • Each comment explains why and offers a concrete suggestion, not just "this is wrong"
  • At least one specific thing done well is noted
  • A clear verdict (approve / request changes) with the gating issues named
  • Tone is direct but kind — critiques the code, not the author

Anti-Patterns

  • Do not nitpick style while missing a correctness or security problem — priority first
  • Do not dump ungraded comments — rank them so the author knows what's blocking
  • Do not say "this is wrong" without why and a suggested fix
  • Do not rewrite it your way for taste — respect working approaches; flag real issues
  • Do not be a jerk — review the code, acknowledge good work, keep the author motivated

Based On

Senior code-review practice (Google's engineering review guidelines): prioritize correctness/design, severity-tag feedback, be kind.

Example Trigger Phrases

  • "Review code."
  • "Give PR feedback."
  • "Review this change."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/code-review-guide of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Code Review Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Review Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Review Guide this skillmohitagw15856/pm-claude-skills1.4k—~931Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence
Open Code Review CLIalibaba/open-code-review44k—~3.1kAutomated safety check: PassApache-2.0
GitHub Review Iterationprisma/orm48k—~2.2kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    44k GitHub stars~3.1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Code Review

    flutter/flutter

    Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.

    179k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,322 skills in this repo
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Offer Comparison

    mohitagw15856/pm-claude-skills

    Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Refinance Breakeven

    mohitagw15856/pm-claude-skills

    Compute the month a refinance actually starts saving money — payment delta, breakeven month, and total interest on both paths including the term-reset trap.

    1.4k GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Rent Vs Buy

    mohitagw15856/pm-claude-skills

    Model rent-vs-buy honestly — year-by-year net position for both paths including the assumption everyone drops (the renter invests the difference), with a breakeven horizon instead of a verdict.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Code Review Guide

What does Code Review Guide do?

Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters. Code Review Guide is an agent skill from mohitagw15856/pm-claude-skills. Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters.

When should I use Code Review Guide?

Code Review Guide fits situations like: giving PR feedback; asked to review this change.

How do I install Code Review Guide in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill code-review-guide -a claude-code`. Or copy the skill folder (skills/code-review-guide in mohitagw15856/pm-claude-skills) into .claude/skills/code-review-guide in your project. Claude Code loads it when a task matches its description.

How do I install Code Review Guide in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill code-review-guide -a codex`. Or copy the skill folder (skills/code-review-guide in mohitagw15856/pm-claude-skills) into .agents/skills/code-review-guide in your project. Codex loads it when a task matches its description.

Can I use Code Review Guide in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill code-review-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review-guide, .gemini/skills/code-review-guide, .github/skills/code-review-guide and .opencode/skills/code-review-guide in your project.

What does Code Review Guide need to run?

SKILL.md names no scripts, command-line tools or credentials: Code Review Guide is instructions for the agent only.

Does Code Review Guide access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Code Review Guide safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Code Review Guide use?

Code Review Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Review Guide use?

About 931 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Review Guide?

Skills that share tags, products or a category with Code Review Guide: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars) and Open Code Review CLI (alibaba/open-code-review, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Review Guide?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,431 GitHub stars. The repository holds 1,322 skills in this directory. The repository was last updated on October 7, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.