review-changes

Reviews a git diff against the Code Review Pyramid and produces a single merge verdict.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often blur blocking defects with personal preferences, leaving authors unsure what actually gates a merge. This Skill reviews the diff between HEAD and a fixed point (commit, branch, tag, or merge-base) against the Code Review Pyramid, checks conformance to the originating spec and repo standards, and resolves every finding into one clear verdict: Approved, Approved with suggestions, or Request changes. ## Core Features & Use Cases - Pyramid-driven review: Loads the Code Review Pyramid and works through every layer, spending the most attention on API and implementation semantics and the least on code style. - Spec and standards checking: Locates the originating issue or spec from commit messages, branch names, or local docs, and enforces documented repo conventions and contract docs like READMEs and OpenAPI schemas. - Structured verdict report: Sorts findings into blocking requested changes and non-blocking suggestions, each tagged by layer with file:line citations, plus a checked-and-clean section and a path to merge. - Use Case: Before merging a feature branch, ask for a review since main. The Skill captures the diff, verifies test status from CI or by running the suite, accounts for every spec requirement, and returns a verdict-led report the author can act on. ## Quick Start Review my changes since main and tell me whether this branch is ready to merge.

Frequently Asked Questions about review-changes

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

FAQPage Schema
How do I review a git diff before merging a branch?▼

Provide a fixed point such as a commit SHA, branch name, tag, or main, and the review captures the diff with git diff using the three-dot merge-base comparison. Every finding is sorted into blocking requested changes or non-blocking suggestions, ending in one verdict.

What is the Code Review Pyramid in code review?▼

The Code Review Pyramid orders review attention by what a mistake costs to unwind, with API semantics at the base and code style at the apex. Reviewers spend the most effort on API and implementation semantics and the least on style, which automation should handle.

Can I review changes without a spec or issue ticket?▼

Yes, the review proceeds without a spec when none exists, but the report is marked as spec-less with a caveat in the summary. The reviewer is told explicitly that conformance to requirements was never assessed.

Does this review run the test suite or rely on CI results?▼

It uses an existing CI or pipeline signal when one is available and runs the test suite directly when the repo has no CI. Test status is reported as unverified only when no signal exists, and skipped or disabled tests count as unverified coverage.

What is the difference between a requested change and a suggestion?▼

A requested change blocks the merge and covers production defects, unintended breaking changes to user-facing contracts, missing spec requirements, and hard breaches of documented standards. A suggestion covers judgment calls, optional refactors, and style preferences the author may decline.