What problem does it solve? When you change front-end code, it is hard to know whether the change broke the interface somewhere else. This Skill reviews a change (a branch, pull request, or working tree) rather than a single screen, expanding changed files to the surfaces they affect and classifying every finding as Introduced, Regression, or Pre-existing. ## Core Features & Use Cases - Scope Resolution: Automatically resolves the review target from git state, handling branches, PRs, uncommitted changes, shallow clones, and mid-rebase states, while excluding lockfiles, snapshots, and generated output. - Removed-Signal Detection: Reads the deleted side of every diff hunk to catch removed accessibility attributes, focus styles, motion preferences, and text signals that a post-change-only review would miss. - Classified Findings Report: Produces a scope block, coverage table, and findings table with severity, status, and before/after evidence, ending in an Approve or Block verdict. - Use Case: Before merging a pull request that refactors a shared Button component, run the review to confirm no consumer lost its focus indicator, aria-label, or disabled state. ## Quick Start Ask the assistant to review the interface impact of your current branch or a specific pull request, for example by requesting an interface review of PR 482.
