What problem does it solve? Code review tools focus on correctness, tests, and security, but nobody checks whether a pull request broke the interface. This Skill reviews a change (a branch, PR, or working tree) rather than a 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: Resolves review targets like pr 482, a branch, a range, or uncommitted changes against the merge base, excluding lockfiles, snapshots, and generated output. - Blast Radius Expansion: Expands changed files to their consumer surfaces (one hop, two for design tokens and shared primitives) so a diff is reviewed where it actually renders. - Removed-Signal Detection: Reads the - side of every hunk for removed accessibility attributes, focus styles, motion preferences, and text signals, routing each to the owning domain skill. - Use Case: Run /interface-review pr 482 before merging to get a scope block, a coverage table, and a findings table with severity, status, and before/after evidence, ending in an Approve or Block verdict. ## Quick Start Ask the agent to run interface-review on your current branch or a specific pull request, for example: review pull request 482 for interface regressions.
