code-review

Review a git diff against coding standards and the originating spec in parallel sub-agents.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/sndrgrdn/skills --skill code-review-sndrgrdn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/sndrgrdn/skills/tree/main/code-review
Command: npx skills add https://github.com/sndrgrdn/skills --skill code-review-sndrgrdn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a branch or PR requires checking two separate things at once: whether the code follows the repo's documented standards, and whether it actually implements what the issue or spec asked for. Mixing both in one pass lets one axis mask the other, so findings get lost or misranked. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (documented repo standards plus a Fowler code-smell baseline) and a Spec review (requirements coverage, scope creep, wrong implementations) as parallel sub-agents, then reports them side by side. - Fixed-point diffing: Reviews the diff between HEAD and any commit, branch, tag, or merge-base the user supplies, validating the ref and diff before spawning agents. - Spec discovery: Locates the originating spec from issue references in commit messages, a user-provided path, or spec files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review since main and receive separate Standards and Spec reports, each with cited findings and a per-axis summary. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a branch against coding standards and its spec?▼

Provide a fixed point such as a commit SHA, branch, tag, or main, and the skill diffs HEAD against it using a three-dot merge-base comparison. It then runs a Standards sub-agent and a Spec sub-agent in parallel and reports both sets of findings side by side.

How do I review changes since a specific commit or tag?▼

Pass any git ref as the fixed point, including commit SHAs, tags, branch names, or expressions like HEAD~5. The skill validates the ref with git rev-parse and confirms the diff is non-empty before starting the review.

What happens if there is no spec or issue for the changes?▼

The skill searches commit messages for issue references, checks user-provided paths, and looks under docs/, specs/, and .scratch/ for a matching spec. If none exists, the Spec sub-agent is skipped and the final report notes that no spec was available.

Does the review work when a repo has no documented coding standards?▼

Yes. A built-in baseline of Fowler code smells, such as Duplicated Code, Feature Envy, and Shotgun Surgery, always applies. Documented repo standards override the baseline, and baseline smells are reported as judgement calls rather than hard violations.

Why are standards and spec findings reported separately?▼

A change can pass one axis and fail the other, such as clean code that implements the wrong thing. Keeping the reports separate under distinct headings prevents one axis from masking or reranking the other's findings.