change-review

Reviews and fixes uncommitted working diffs before commit using repository guidance and targeted tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Uncommitted changes often accumulate style issues, unnecessary complexity, weak tests, and convention violations that authors overlook in their own diffs. This Skill performs a fresh-context review of the working diff and fixes problems directly before commit, rather than producing a report of suggestions. ## Core Features & Use Cases - Fresh-context subagent review: Dispatches a general-purpose subagent with empty context to review the uncommitted diff without author bias, reading the full diff and untracked files before editing. - Direct cleanup, not reporting: Applies the repository review checklist to cut dead code, rename, flatten, and restructure, while fixing lint findings at their source. - Narrowest credible verification: Selects focused tests or layers matching the changed surface, runs scripts/lint.sh, and reports honest blocked or skipped capabilities. - Use Case: After finishing an ad-hoc bug fix in a Lua/LÖVE repository, invoke this Skill to have a fresh reviewer clean the diff, remove speculative helpers, run the affected test layer plus lint, and return a summary of changes and verification status. ## Quick Start Ask the AI to run the change-review skill on the current uncommitted working diff and fix any issues it finds before commit.

Frequently Asked Questions about change-review

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

FAQPage Schema
How do I review uncommitted changes before committing?

Run this Skill on the working tree; it derives scope from git status and git diff HEAD, reads the full diff including untracked files, fixes issues directly, and runs targeted tests plus lint before summarizing the cleanup.

What is a fresh-context code review?

A fresh-context review dispatches a subagent with empty context that receives only the skill instructions and repository path, not author notes or failed approaches. This removes bias so the reviewer evaluates the diff on its own merits.

When should I use change-review instead of branch-review?

Use change-review for standalone ad-hoc uncommitted work before commit. Spec-based development defers generic cleanup to the integrated branch review, which owns the exhaustive final gate and prevention retrospectives.

Does the review run the full test suite every time?

No. It selects the narrowest credible verification, such as focused tests or an affected layer, and reserves the full suite for broad composition, test runner, or shared architecture changes. Lint always runs.

Can the review delete code from my diff?

Yes, it cuts branches, fallbacks, helpers, and tests that lack a current caller, contract, or failure mode. It never deletes necessary correctness or safety code just to improve the line delta.