code-review

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

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

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 originating issue or spec asked for. Doing 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 fixed Fowler code-smell baseline) and a Spec review (requirements coverage, scope creep, incorrect 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 that the ref resolves and the diff is non-empty. - Spec discovery: Locates the originating spec from issue references in commit messages, a user-supplied 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 git 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 three-dot comparison. It then runs two parallel sub-agents: one checks documented standards plus a Fowler code-smell baseline, the other checks the diff against the originating spec.

How does the review find the spec for a branch?▼

It looks for issue references in commit messages first, then a user-supplied path, then spec files under docs/, specs/, or .scratch/ matching the branch or feature. If nothing is found, it asks the user, and the Spec axis is skipped when no spec exists.

What code smells does the standards review check for?▼

The baseline covers twelve Fowler smells including Duplicated Code, Feature Envy, Data Clumps, Primitive Obsession, Shotgun Surgery, and Speculative Generality. Each is reported as a labelled judgement call, and documented repo standards always override the baseline.

What happens if the fixed point or diff is invalid?▼

The skill validates the fixed point with git rev-parse and confirms the diff is non-empty before spawning any sub-agents. A bad ref or empty diff fails immediately at that step rather than inside the parallel review agents.

When should I not use this two-axis review approach?▼

It is less useful when there is no spec or issue behind the change, since the Spec axis will be skipped, or when tooling already enforces the relevant standards, since those checks are deliberately excluded from the review.