Guide · Agent skill
How to use the Interface Change Review agent skill (interface-review)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The interface-review skill is an agent skill that reviews a code change for user-interface problems it caused: accessibility, layout, writing, typography, color and UI. It is for developers and front-end teams who want a second look at a pull request's UI impact before merging. After this guide you will know what the skill does, how to install it, how to ask for a review in plain language, and what it needs to run.
Interface Change Reviewjakubkrehel/skills · MIT Download the skill Quick start
- 1Install git and gh if needed. Make sure git is available. For a pull request review, also install the GitHub CLI (gh).
- 2Install interface-review. Unzip the downloaded ZIP into ~/.claude/skills/ or a project's .claude/skills/, or upload it under Settings, Capabilities, Skills.
- 3Install better-interface. Add the companion better-interface skill and its related better-* domain skills, since the review depends on them.
- 4Check your change is in place. Make sure your branch has commits ahead of its base, or that you have uncommitted changes, so there is something to review.
- 5Ask for a review. Run /interface-review with a target such as pr 482, or with no target to review your branch and uncommitted work.
- 6Read the findings. Check the scope block first, then each finding's status: Introduced, Regression or Pre-existing.
What the interface-review skill makes the agent do
The skill reviews a change, not a whole screen or codebase. It works out which change to review (a pull request, a branch, or uncommitted work), finds the screens that change affects, and reads both the removed lines and the added ones.
Each finding is labelled as Introduced (the change created it), Regression (the change weakened something that was previously correct) or Pre-existing (already there before the change and not made worse by it). The severity rules and final verdict are handed to a companion skill called better-interface.
- Resolves the scope: a pull request, branch or uncommitted changes
- Expands changed files to the surfaces they affect
- Checks removed lines for lost labels, focus indicators, reduced-motion handling and similar signals
- Labels every finding as Introduced, Regression or Pre-existing
Install the interface-review skill
Option 1: download the ZIP from this page and unzip it into your personal skills folder, ~/.claude/skills/, or into a project's .claude/skills/ folder for use in one repository.
Option 2: in the Claude apps, open Settings, then Capabilities, then Skills, and upload the ZIP there.
The skill package contains agents/openai.yaml, removed-signals.md, scope-resolution.md and SKILL.md. Keep these files together in the same folder.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside the repository
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
Install the companion better-interface skill
interface-review does not decide severity, consolidate findings or give the verdict. It hands those to better-interface, and it relies on the related better-* domain skills for the actual rules, such as better-accessibility and better-colors.
Without better-interface installed, the skill stops and reports only the scope and file inventory. It will not invent a severity scale or verdict.
- Required: better-interface
- Related domain skills it refers to: better-accessibility, better-colors
Trigger the skill with natural requests
The skill is invoked with a slash command followed by a target. Targets the source accepts are working, staged, branch, pr <n>, a bare ref, and an explicit a..b or a...b range. With no target, the skill looks at the branch against its base first, then at uncommitted changes.
If there is no change to review, the skill will not pick one for you. It reports the facts and offers options, such as the open pull request, the last commit, or a target you name.
- /interface-review pr 482 reviews pull request 482
- /interface-review with no target reviews your branch, then uncommitted changes
- /interface-review staged or /interface-review working for specific local work
- /interface-review main..my-branch for an explicit range
/interface-review pr 482Read the report: scope, statuses and what was not verified
The report begins with a scope block that names the base commit and counts for commits and uncommitted files. Each finding carries one status, so you can tell what your change caused from what was already there.
Visual and runtime claims are marked Not verified unless the project exposes a cheap preview or you ask for a rendered review. Rendering is read-only: the skill does not switch branches or change your open files.
- Scope block: base commit, commit count, uncommitted file count, excluded files
- Statuses: Introduced, Regression, Pre-existing
- Rendered checks are opt-in and marked Not verified otherwise
Safety notes: scripts and network access
The skill runs scripts and uses the network. It runs git diff, merge-base and blame commands, and uses the GitHub CLI (gh) to read pull request details when you review a PR. Fetching is permitted because it only writes to the .git folder.
The skill is designed not to modify your working tree. It does not run gh pr checkout, git checkout, git switch or git stash, so the files you have open are not rewritten.
- Requires git and, for PR reviews, the GitHub CLI (gh)
- Runs scripts and uses the network
- Read-only with respect to your files; git fetch is allowed
What people use it for
- Checking a pull request's UI impact before merging
- Confirming a design token or shared component change did not break other screens
- Catching a removed aria-label, focus outline or reduced-motion check in a diff
- Reviewing only what a specific branch changed, rather than the whole codebase
Frequently asked questions
How do I install the interface-review skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps you can instead upload the ZIP under Settings, Capabilities, Skills.
What does the interface-review skill require?
It requires git, since it runs git diff, merge-base and blame commands. For pull request reviews it also needs the GitHub CLI (gh). It also needs the companion better-interface skill and its related better-* domain skills, or it stops after reporting scope.
Is interface-review free to use?
The source identifies the skill's licence as MIT. It does not state any price, so check the repository for licence terms.
Does interface-review check security, performance or correctness?
No. The skill explicitly leaves correctness, tests, security and performance to the project's general code review.
Can interface-review audit my whole app's design?
Not as a change review. It is scoped to a change and hands a whole-repository interface audit to better-interface as a repository-scope review.
Will the skill change my files or switch branches?
No. The skill is built to be read-only with respect to the working tree. It does not run gh pr checkout, git checkout, git switch or git stash, though git fetch is allowed.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use interface-review if you want a focused check of what a pull request or branch did to the interface, with each finding marked as new, a regression or pre-existing. Pick something else if you need a whole-app design audit, a security or performance review, or if you cannot install the better-interface companion skill.
Download the skill