review-change

Audit git working tree diffs read-only and report severity-grouped findings.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/0xdeafcafe/skills --skill review-change-0xdeafcafe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-change
Source: https://github.com/0xdeafcafe/skills/tree/main/skills/review-change
Command: npx skills add https://github.com/0xdeafcafe/skills --skill review-change-0xdeafcafe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives you a rigorous, read-only audit of your current code changes when you want a trustworthy verdict before you fix anything. It helps catch code quality, testing, feature, security, hygiene, and UI issues across staged, unstaged, committed-but-unpushed, and untracked work without modifying files or creating commits.

Core Features & Use Cases

  • Full diff auditing: Reviews the working tree scope across staged, unstaged, untracked, and recent branch changes against a sensible base.
  • Specialist review pipeline: Routes the change through multiple focused reviewers for code, tests, feature behavior, security, hygiene, and optionally UX or spec-related concerns.
  • Structured findings only: Produces a single terminal report grouped by severity so you can act on concrete findings instead of vague commentary.
  • Scales by change size: Uses adaptive triage for tiny, small, and large diffs, including slice, merge, and verification phases for more complex changes.
  • Use case: Before opening a PR, ask for a read-only audit of your working tree to identify risky regressions, missing tests, insecure patterns, and cross-slice contract issues while keeping full manual control over the fixes.

Quick Start

Ask the agent to review the change or audit your working tree diff read-only without fixing anything.

Frequently Asked Questions about review-change

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

FAQPage Schema
How do I audit my git working tree diff without modifying files?

You can audit a git working tree diff read-only by collecting staged, unstaged, untracked, and committed-but-unpushed changes, then routing them through specialist reviewers to report structured findings without modifying files or committing.

Can I run a security and test review on unpushed git changes?

Yes, a security and test review can run on unpushed git changes by evaluating the working tree diff against a base branch, applying specialist review pipelines to identify insecure patterns and missing tests before opening a PR.

What is the best way to review large code changes before a PR?

Reviewing large code changes before a PR requires adaptive triage that slices large diffs, processes them through parallel specialist reviews, and merges verified results into a severity-grouped terminal report.

Does read-only code review work for untracked files in the working tree?

Read-only code review supports untracked files in the working tree by including them in the diff collection alongside staged and unstaged changes, auditing feature correctness and hygiene without altering the files.

How do I get structured findings from a working tree audit?

Structured findings from a working tree audit are generated by routing the diff through focused reviewers for code, tests, and security, producing a single terminal report grouped by severity to help you act on concrete issues.

When should I avoid automated code fixes during a security audit?

Avoid automated code fixes during a security audit when you need full manual control, using a read-only audit to identify risky regressions and insecure patterns before applying fixes yourself.