interface-review checks a change, where most UI reviews check a screen. It resolves which commits and files are in scope, expands the changed files to the surfaces that render them, reads the removed lines of the diff for lost accessibility and typography signals, and labels each finding as Introduced, Regression or Pre-existing.
The review is read-only. It never checks out branches or stashes work, and it hands the actual domain judgement and the final verdict to the better-interface skill. You invoke it yourself by command.
What You Get
- A scope block naming the target, base and head refs, commit counts, files in scope, exclusions and surfaces expanded
- A findings table with severity, domain, status, location, before, after and reason
- Regressions found by scanning removed lines for aria attributes, focus styles, reduced-motion queries, logical properties and similar signals
- Up to three pre-existing findings, stated as outside the change’s responsibility
- Checks that the change delivers its stated intent, such as missing hover, focus, disabled or loading states and untranslated strings
Common Use Cases
- Reviewing a pull request for accessibility or layout regressions before merge
- Checking a feature branch that adds a new component for missing states
- Checking uncommitted work for removed aria-label or focus outlines
- Reviewing a design-token change for the consumers it affects
What Makes It Unique
It reviews a diff and its blast radius. Findings are statused by cause, so a problem a changed token creates in an untouched component counts as Introduced. It reads the removed side of each hunk against a table of signals and the equivalent replacements that clear them, handles awkward states such as shallow clones, detached HEAD and mid-rebase trees, and refuses to invent a change when none exists.
Under The Hood
The skill is written instructions plus two reference files, one on removed signals and one on resolving scope. The agent runs read-only git commands in your shell, including diff, blame, grep, show, merge-base and fetch, and uses the GitHub command-line tool for pull request details. Fetching writes only inside the .git folder and may use the network, and a git worktree under the temporary folder may be created for rendered checks and removed after. It never checks out or stashes your files. It can run a project preview when you ask for a rendered review. Domain rules and the verdict come from the better-interface skill.