code-review

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

Updated Nov 10, 2013
One-click install
npx skills add https://github.com/bnferguson/dotfiles --skill code-review-bnferguson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/bnferguson/dotfiles/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/bnferguson/dotfiles --skill code-review-bnferguson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often conflate two separate questions: does the code follow the project's standards, and does it actually implement what was asked for? This Skill separates those axes so one cannot mask the other, and runs both checks in parallel sub-agents to keep their contexts clean. ## Core Features & Use Cases - Two-axis review: Evaluates the diff against documented repo standards (plus a built-in Fowler code-smell baseline) and against the originating issue or spec, reported side by side. - Parallel sub-agents: Spawns independent Standards and Spec sub-agents so findings from one axis never pollute or rerank the other. - Flexible fixed points: Reviews any diff from a commit, branch, tag, or merge-base (e.g. main, HEAD~5) using three-dot diff semantics. - Use Case: Before merging a feature branch, ask for a review since main and receive a Standards report citing violated conventions and smells, plus a Spec report listing missing requirements and scope creep. ## Quick Start Ask the assistant to review the changes on this branch since main against the 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 before merging?▼

Provide a fixed point such as main, a commit SHA, or a tag, and the skill diffs HEAD against it using three-dot merge-base semantics. It then checks the diff against documented repo standards plus a built-in Fowler code-smell baseline.

How do I check if code matches the original issue or spec?▼

The Spec axis locates the originating spec from issue references in commit messages, a user-provided path, or files under docs/, specs/, or .scratch/. It reports missing requirements, scope creep, and implementations that look wrong, quoting the spec for each finding.

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

If no spec is found and the user confirms none exists, the Spec sub-agent is skipped and the final report notes that no spec was available. The Standards review still runs normally.

Why does the review report standards and spec findings separately?▼

The two axes are kept separate so one cannot mask the other: code can follow every standard but implement the wrong thing, or match the spec while breaking project conventions. Findings are never merged or reranked across axes.

What code smells does the standards review check for?▼

The baseline covers Fowler smells including Duplicated Code, Feature Envy, Data Clumps, Primitive Obsession, Shotgun Surgery, Divergent Change, and Speculative Generality. Documented repo standards always override the baseline, and smells are reported as judgement calls, not hard violations.