code-review

Reviews a git diff against coding standards and the originating spec using parallel sub-agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a branch or PR requires checking two independent questions at once: does the code follow the repo's documented standards, and does it actually implement what the issue or spec asked for. Doing both in one pass lets one axis mask the other, so problems slip through. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (documented repo conventions 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: Compares HEAD against any user-supplied commit, branch, tag, or merge-base using three-dot git diff, with upfront validation of the ref and diff. - Spec discovery: Locates the originating spec from issue references in commit messages, user-provided paths, or 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 citing the violated rule or spec line. ## Quick Start Ask the agent to review the changes on this branch since main against the repo's coding standards and the originating issue.

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, or tag, and the review compares HEAD against it using a three-dot git diff. Two parallel sub-agents check standards compliance and spec coverage, then report findings side by side.

How to review changes since a specific commit in git?▼

Specify any ref like main, HEAD~5, a tag, or a SHA as the fixed point. The skill validates the ref with git rev-parse, confirms the diff is non-empty, and reviews git diff <fixed-point>...HEAD against the merge-base.

What happens if there is no spec for the changes being reviewed?▼

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

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

Yes. A built-in baseline of Fowler code smells from Refactoring chapter 3 always applies, covering issues like Duplicated Code, Feature Envy, and Shotgun Surgery. Documented repo standards override the baseline where they conflict.

Why are standards and spec findings reported separately?▼

A change can follow every standard but implement the wrong thing, or match the spec while breaking conventions. Keeping the axes separate prevents one passing axis from masking failures in the other, so findings are never merged or reranked.