What is the interface-review skill?
The interface-review skill reviews a change instead of a screen. It resolves the scope, expands changed files to the surfaces they affect, reads the removed lines, and labels every finding Introduced, Regression or Pre-existing. It is user-invoked, read-only, and hands severity and the verdict to better-interface.
Interface-review answers one question for an author: did I make this worse? It reports what the change caused and stays mostly quiet about what it merely touched. Three pre-existing findings is a courtesy, and thirty is a different review.
You invoke it with a target, so a command naming pull request 482 reviews that pull request. With no target it picks the branch range plus uncommitted changes, then a dirty working tree, and otherwise asks.
How it reviews a change
- Resolve the scope and record the base commit of the range.
- Expand changed files one hop to direct importers, and a second hop only for tokens, themes and shared primitives, reviewing at most five consumers.
- Read the removed lines against a list of removed signals, since regressions hide in the pre-change state.
- Classify each finding as Introduced, Regression or Pre-existing, using git blame on the reviewed range.
- Check the stated intent in the pull request title, body and commits for absent states.
Read only by design
The skill never rewrites the working tree. Fetching refs is allowed, but checkout, switch and stash are not, because they change files the author has open. Rendered checks are opt-in, and unrun checks are marked Not verified.
Who it suits
Best for
- Pull requests that touch shared components, tokens or theme values.
- Catching a deleted aria-label, an outline removal or a lost reduced-motion guard.
- Spotting incomplete changes such as a new variant missing a disabled state.
Not for
- Correctness, tests, security and performance. It names such a concern once and points at your general code review.
- A whole screen audit, which belongs to better-interface. Related: critique, impeccable-audit and web-quality-audit.
Use it with UiChemy
Review the diff your agent produced for the front end before moving on. Pages that start from a design can still come into WordPress through UiChemy Figma to WordPress or Composer. This skill reviews code changes only. Get Started on uichemy.com.
How to install Interface Review Skill: Audit a Branch or Pull Request
git clone https://github.com/jakubkrehel/skills.gitClone the repository
Run
git clone https://github.com/jakubkrehel/skills.git. The skill is in skills/interface-review.Install better-interface with it
Copy skills/interface-review and skills/better-interface, plus the domain skills it routes to, into your agent's skills folder. Keep removed-signals.md and scope-resolution.md beside SKILL.md.
Plugin option for Claude Code
Run
/plugin marketplace add jakubkrehel/skillsand/plugin install interfaces@interfaces, the commands in the README.Invoke it on a change
Run /interface-review with a target such as pr 482, a branch or a range. With no target, it reviews your branch and uncommitted work.
Check that it loaded
Run it on a small branch. The output should open with a scope block, then a coverage table, then findings labelled Introduced, Regression or Pre-existing, ending in a verdict such as Approve.
Key features
- Change scope resolutionA named target is reviewed as given. Otherwise it reviews the branch range plus uncommitted changes, then a dirty tree, and states commit and file counts separately.
- Asks rather than inventsWith no change to review it never falls back to the last commit on its own. It offers the open pull request, the last commit, a named target or a repository audit.
- Excluded pathsLockfiles, snapshots, generated output, vendored code and binaries are left out, and the report names what was excluded. An empty scope is never reported as Approve.
- Blast radius expansionA changed file is evidence and its consumers are the subject. The skill expands one hop, two for tokens and shared primitives, with at most five consumers and an unexpanded count.
- Removed line readingIt reads the minus side of every hunk against a list of removed signals and routes each unmatched removal to the domain skill that owns the judgment.
- Three status labelsEvery finding is Introduced, Regression or Pre-existing, set by cause and not by location, so an untouched consumer of a changed token still counts against the change.
- Intent checkIt reads the pull request title and body, the linked issue and the commits, and looks for absent states, missing translation entries and controls added to one surface but not its siblings.
- Hands off to better-interfaceSeverity, consolidation, coverage, the cap and the verdict come from better-interface. If it is missing, the skill reports scope and inventory and stops.
- Read only checkout rulesFetch is allowed, but checkout, switch and stash are not. A non-local target renders in an isolated worktree that is removed afterward.
- Structured outputA scope block opens the report, then a coverage table and a findings table with a status column. Pre-existing items are capped at three.
Frequently asked questions
What is the interface-review skill?
It is a skill in Jakub Krehel's skills repository that reviews a branch, pull request or uncommitted change for interface problems the change introduced or regressed, across accessibility, layout, writing, typography, color and UI. It is user-invoked rather than triggered by the model.
How do I install interface-review?
Clone jakubkrehel/skills and copy skills/interface-review, with its two reference files, into your agent's skills folder along with better-interface. In Claude Code you can run the plugin marketplace add and plugin install commands from the README instead.
What targets can I give it?
The whole invocation is the target, so pr 482 reviews pull request 482, and a branch, ref or range works the same way. With none, it reviews your branch range plus uncommitted changes, then a dirty working tree, and asks you when there is no change to review.
What do the finding statuses mean?
Introduced means the change created the problem, Regression means it weakened something previously correct, and Pre-existing means the problem was there before and was not made worse. Status follows cause, not location, and blame on the reviewed range settles doubtful lines.
Will it change my working tree?
No. A change review is read only, including the checkout. Fetching refs is permitted, but gh pr checkout, git checkout, git switch and git stash are never used, because they rewrite files you may have open. Rendered checks use an isolated worktree for other targets.
Which AI coding agents can use interface-review?
The README documents a Claude Code plugin install, and the skill folder includes an agents/openai.yaml file. For other agents, copy the folder to their skills location. The README lists no other agents, so confirm yours reads SKILL.md folders.
Does it replace my normal code review?
No. Correctness, tests, security and performance belong to your general review. Interface-review mentions such a concern once, points at that review and drops it, then keeps its attention on interface problems the change caused.