review-change

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

28|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NauelG/astro-blocks --skill review-change-nauelg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-change
Source: https://github.com/NauelG/astro-blocks/tree/main/.agents/skills/review-change
Command: npx skills add https://github.com/NauelG/astro-blocks --skill review-change-nauelg

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? This Skill separates those axes so one cannot mask the other, and automates the review of any branch, PR, or work-in-progress diff. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (repo-documented conventions plus a Fowler code-smell baseline) and a Spec review (fidelity to the originating issue or spec) as parallel sub-agents, then reports them side by side. - Fixed-point diffing: Reviews changes since any commit, branch, tag, or merge-base using three-dot git diff, with upfront validation of the ref and diff. - Automatic 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 assistant to review the changes on this branch since main using the review-change skill.

Frequently Asked Questions about review-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review all changes on a branch since main?▼

Provide the fixed point (e.g., main) and the skill runs git diff with three-dot notation against the merge-base, then reviews the diff on two axes: standards compliance and spec fidelity. Results are reported under separate Standards and Spec headings.

What coding standards does an automated code review check?▼

It checks any standards documented in the repo, such as CODING_STANDARDS.md or CONTRIBUTING.md, plus a baseline of Fowler code smells like Duplicated Code, Feature Envy, and Shotgun Surgery. Documented repo standards always override the baseline.

Can a code review verify changes against the original issue or spec?▼

Yes. The Spec axis locates the originating spec from issue references in commit messages, a user-provided path, or files under docs/, specs/, or .scratch/, then reports missing requirements, scope creep, and incorrect implementations with quoted spec lines.

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 fail before the sub-agents run?▼

The skill validates the fixed point with git rev-parse and confirms the diff is non-empty before spawning sub-agents. An unresolvable ref or empty diff fails fast at that step rather than inside the parallel reviews.