review

Reviews git diffs against coding standards and originating specs using parallel sub-agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often conflate two separate questions: does the code follow the project's documented standards, and does it actually implement what the issue or spec asked for? This Skill separates those axes so one cannot mask the other, and offloads each review to an isolated sub-agent for unbiased 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 and receive side-by-side Standards and Spec reports citing violated rules and unmet requirements. ## Quick Start Ask the assistant to review the changes on this branch against main using the review skill.

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 review skill diffs HEAD against it using three-dot git diff. 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 or 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 files count as coding standards sources?▼

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

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

The skill compares HEAD against a fixed point using git diff, so uncommitted working-tree changes are not included in the three-dot comparison. 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 follow every standard but implement the wrong thing, or meet the spec while breaking project conventions. Keeping the two axes in separate reports prevents one axis from masking failures in the other.