What problem does it solve? Code changes often introduce subtle interface regressions—removed ARIA labels, dropped focus styles, missing component states—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 and excluding lockfiles, snapshots, and generated output. - Blast Radius Expansion: Expands changed files to the surfaces that render them (one hop, two for design tokens), reviewing up to five consumers with a stated cutoff. - Removed-Signal Detection: Reads the - side of every hunk to catch removed accessibility attributes, focus indicators, motion preferences, and text signals, routing each to the owning domain skill. - Use Case: Before merging a pull request that refactors a shared Button component, run the review to confirm no consumer lost its focus ring, accessible name, or disabled state, and receive a severity-ranked findings table with a Block or Approve verdict. ## Quick Start Ask the assistant to run an interface review on pull request 482 and report any introduced or regressed findings.
