review

Reviews git diffs against coding standards and spec requirements using parallel sub-agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often conflate two separate questions — does the code follow project conventions, and does it implement what was actually requested — causing one axis to mask failures in the other. This Skill separates those concerns into independent parallel reviews so neither axis hides the other's findings. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (against CLAUDE.md, CONTRIBUTING.md, ADRs, style guides) and a Spec review (against the originating issue or PRD) as parallel sub-agents. - Flexible fixed point: Reviews the diff between HEAD and any commit, branch, tag, or merge-base the user supplies, using three-dot git diff semantics. - Automatic spec discovery: Locates the originating spec from issue references in commit messages, user-provided paths, or PRD files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review against main to get a side-by-side report of standards violations and spec gaps, each citing the exact rule or requirement line. ## Quick Start Ask the assistant to review the current branch against main using the review skill, and point it to the relevant issue or spec file if one exists.

Frequently Asked Questions about 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 three-dot git syntax. It then runs two parallel sub-agents: one checks the diff against documented standards, the other against the originating issue or PRD.

How does the review skill find the spec for a change?▼

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

What files count as coding standards sources?▼

Standards sources include CLAUDE.md, AGENTS.md, CONTRIBUTING.md, CONTEXT.md files, docs/adr/ decisions, and style guides like STYLE.md or STANDARDS.md. Machine-enforced configs like eslint or tsconfig are noted but not re-checked since tooling already validates them.

Can I review work-in-progress changes that are not committed?▼

The skill compares HEAD against a fixed point via git diff, so uncommitted changes are not included in the diff. Commit your work-in-progress first, or choose a fixed point that captures the range you want reviewed.

Why are standards and spec reviews reported separately?▼

A change can pass one axis and fail the other: standards-compliant code may implement the wrong thing, and spec-correct code may violate conventions. Keeping the reports separate under distinct headings prevents one axis from masking the other's failures.