What problem does it solve? Code changes often introduce subtle interface regressions—removed accessibility attributes, broken focus states, or incomplete component variants—that standard code review misses. This Skill reviews a change (branch, PR, or working tree) rather than a static screen, classifying every finding as Introduced, Regression, or Pre-existing so authors know exactly what their change caused. ## Core Features & Use Cases - Scope Resolution: Accepts targets like pr 482, branch, working, staged, or explicit ranges, resolving them against the merge base while excluding lockfiles, snapshots, and generated output. - Removed-Signal Detection: Reads the - side of every diff hunk to catch deleted ARIA attributes, focus styles, semantic elements, and motion preferences that post-change code alone would hide. - Blast Radius Expansion: Expands changed files to their consumer surfaces (one hop, two for design tokens) and reviews up to five consumers with a stated cutoff. - Use Case: Run /interface-review pr 482 before merging to get a structured report with a scope block, coverage table, severity-ranked findings with statuses, and a Block/Approve verdict handed to the better-interface skill. ## Quick Start Ask the assistant to review pull request 482 for interface regressions using the interface-review skill.
