review-changes

Review code, documentation, and configuration diffs for material problems with evidence-backed findings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a diff consistently is hard: reviewers miss surrounding contracts, conflate severity with confidence, invent findings to avoid empty reports, or treat an unavailable diff as "no issues." This Skill structures diff review so every material finding carries evidence, impact, confidence, and a canonical label. ## Core Features & Use Cases - Effective diff scoping: Establishes the exact reviewed range (commit range, PR diff, or staged/unstaged/untracked files) before reviewing, and reports when no diff can be obtained instead of claiming no issues. - Structured finding contract: Each finding gets one canonical label (must/should/suggestion/question/nit/note), a confidence level, evidence, impact, verification method, and an explicit Unconfirmed premises field so downstream triage needs no re-investigation. - Full re-review reconciliation: On explicit re-review, classifies previous findings as Resolved, Remaining, or New, and tags each New finding as Fix-induced, Newly observable, or Late-discovered. - Use Case: Before merging a pull request, ask for a review of the PR diff; the Skill inspects surrounding contracts, callers, and tests, runs safe non-mutating checks, and returns findings ordered by requested response and impact, plus unchecked scope and residual risk. ## Quick Start Review the current staged and unstaged changes in this repository and report material findings with labels, confidence, evidence, and residual risk without editing any files.

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 pull request diff with an AI agent?▼

Provide the PR's base and head or effective diff and ask for a review. The Skill inspects surrounding contracts, callers, and tests, then reports findings with labels, confidence, evidence, impact, and verification steps without editing files.

How to re-review code after review comments are addressed?▼

For an explicitly requested full re-review, the Skill reconciles each previous finding as Resolved, Remaining, or New and classifies new findings by origin. For ordinary post-fix checks of specific findings, use a fix-validation workflow instead.

Can it review documentation and configuration changes, not just code?▼

Yes. It adapts review dimensions to the change type: factual accuracy and command correctness for documentation, schema validity, precedence, defaults, and rollout impact for configuration, using deterministic checks when available.

What happens when no diff is available to review?▼

The Skill states that the review did not run and identifies the missing input, such as a patch, commit range, PR, or file contents. It never reports an unobtainable diff as "no issues found."

Does the review skill modify files or implement fixes?▼

No. It is strictly read-only: it runs only safe, non-mutating checks and never edits tracked files, installs dependencies, performs external writes, triages findings, or implements fixes.

When should I not use this diff review skill?▼

Do not use it for triaging existing review feedback, validating a specific fix, drafting GitHub comments, summarizing changes, or implementing code. Those tasks belong to adjacent workflows with their own responsibility boundaries.