interface-review
Originally fromjakubkrehel/skills
Installation
SKILL.md
Review the change, not just the code it left behind
A diff is not a surface. The lines a change deletes matter as much as the lines it adds, and the file it touches is rarely the whole of what it affects.
This skill owns change scope only: resolving the target, expanding changed files to affected surfaces, reading both sides of the diff, and classifying each finding. Domain rules belong to the better-* skills. Mode, severity, consolidation, coverage, the cap, the output format, and the verdict belong to better-interface, which this skill hands the review to. Never duplicate or override their rules here.
Correctness, tests, security, and performance belong to the project's general code review. Name the concern once and move on.
Quick Reference
| Category | When to Use |
|---|---|
| Scope Resolution | Targets and commands, default branch, merge-base, PR and fork refs, repository states, nothing to review, renames, exclusions, consumer expansion |
| Removed Signals | What to look for on the - side of a hunk and which skill owns each removal |