review-changes

Runs a multi-agent adversarial review over the working-tree git diff and returns ranked findings.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill review-changes-harivansh-afk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-changes
Source: https://github.com/harivansh-afk/loom-index-e2e/tree/main/skills/review-changes
Command: npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill review-changes-harivansh-afk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual code review of local changes is slow and error-prone, and single-pass AI reviews produce false positives. This Skill fans out one reviewer agent per dimension over your git diff, then adversarially verifies each finding so only confirmed defects reach you. ## Core Features & Use Cases - Multi-Dimension Review: Spawns one code-reviewer finder per dimension (correctness, security, performance, maintainability) over the working-tree and staged diff, falling back to the last commit when the tree is clean. - Adversarial Verification: Pipelines every finding through an independent skeptic agent that tries to refute it against the actual code, cutting false positives before reporting. - Ranked Verdicts: Returns confirmed findings sorted by severity, with Correctness and Security marked as blockers and Performance/Maintainability as warnings. - Use Case: After finishing a substantive change, invoke the skill before declaring the work done; it reviews the diff, reports blockers first, and you fix confirmed Correctness/Security findings in the same turn. ## Quick Start Ask the AI to run the review-changes skill on the current working-tree changes and report any confirmed blockers.

Frequently Asked Questions about review-changes

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

FAQPage Schema
How do I review local git changes with AI before committing?▼

Invoke the review-changes skill after finishing a substantive change. It reviews git diff plus the staged diff (falling back to git show HEAD if the tree is clean), fans out one reviewer per dimension, and reports confirmed blockers first.

What is a multi-agent adversarial code review?▼

It is a review where one finder agent per dimension (correctness, security, performance, maintainability) scans the diff, then an independent skeptic agent tries to refute each finding against the actual code. Only findings the skeptic cannot refute are reported.

Does this skill review remote pull requests?▼

No. It reviews a finished local diff in the working tree, not a remote PR. For reviewing a pull request, use a dedicated PR review command such as /review instead.

Why does the review require git diff --no-ext-diff?▼

The environment sets diff.external = difft globally, so a bare git diff returns difftastic's columnar rendering without +/- prefixes or @@ headers. A finder sweeping that output finds no added lines and falsely reports the change as clean.

What happens if the Workflow tool is unavailable?▼

Run the same shape manually: spawn one code-reviewer agent per dimension over the same diff in a single concurrent message, then adversarially verify each finding yourself before reporting, keeping Correctness and Security as blockers.

When should I skip running the review-changes skill?▼

Skip it for genuinely trivial changes such as a typo, a one-line doc or comment, or a config value with no logic. State the reason in one line and stop; the review is intended for substantive changes.