Interface Review Skill: Review a Branch or PR for UI Regressions

interface-review checks a branch, pull request or uncommitted change for the UI problems it introduced or made worse, and hands the review to better-interface.

Installs: 20.6K; on skills.sh
Stars: 10K; on GitHub
Files: 3; besides SKILL.md
Updated: Oct 2026; last repo commit

You run it yourself with /interface-review, as in /interface-review pr 482. It does not trigger on its own. With no target it reviews commits ahead of the default branch plus uncommitted changes, or just the uncommitted changes. If there is nothing to review, it asks instead of guessing.

It reads the whole diff, including the removed lines, and expands to the components that use the changed files (at most five consumers). Each finding gets a status: Introduced, Regression or Pre-existing. It also checks the change against the pull request description for missing states, like a variant without hover or disabled.

This skill owns scope and classification only. Severity, coverage and the verdict come from better-interface, which uses six domain skills, so install all eight. If better-interface is missing, the skill reports the scope and file list and stops.

Good for

Front-end developers who want a UI check on a branch or pull request before merging
Reviewers checking accessibility, layout, copy, type and color in a diff
Design engineers who want findings labelled as introduced, regression or pre-existing

Install interface-review

Claude Code

Copy this prompt.

Install the interface-review skill in Claude Code. Run this command:

/plugin marketplace add jakubkrehel/skills
/plugin install interfaces@interfaces

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

interface-review hands the review to better-interface, which loads the six better-* skills for accessibility, layout, writing, typography, color and UI polish. Install all eight. The plugin installs the whole collection of 14 skills. Run it in Claude Code as /interface-review, for example /interface-review pr 482.

From the project README. Source.

What's in the skill

When it loads

Reviews a branch, pull request or uncommitted change for the interface problems it introduced or regressed, across accessibility, layout, writing, typography, color and UI.

Sections in SKILL.md

The change, not the codebase
1. Resolve the change scope first
2. With no change, ask rather than invent one
3. A diff is not a surface
4. Read the removed lines
5. Classify every finding
6. Hold the change to its stated intent
7. Hand the review to better-interface
Never mutate the working tree
Before you finish
Review output format

Key facts

Author: Jakub Krehel (GitHub: jakubkrehel)
Repo: jakubkrehel/skills
Installs on skills.sh: 20,617 as of 2026-11-02
GitHub stars (whole repo): 10,003 as of 2026-11-02
License: MIT
Last repo commit: 2026-10-25
Files in the skill folder: 4 files including SKILL.md
skills.sh audits: Gen Agent Trust Hub pass, Socket pass, Snyk warn

What it includes

Branch range plus uncommitted work, or a named target
Accepts targets such as pr <n>, a branch, a ref or a range. Excludes lockfiles, snapshots, generated and vendored files.
Runs code · Resolve the scope
Review surfaces that use the changed files
One hop by default, two for design tokens and shared primitives, capped at five consumers with the skipped count stated.
Read · Expand to consumers
Check deleted aria-labels, outlines and reduced-motion rules
References removed-signals.md. A removal is a regression only when nothing in the change replaces it.
Read · Read the removed lines
Introduced, Regression or Pre-existing
Uses git blame against the reviewed range to tell whether a line predates the change. Pre-existing findings are capped at three.
Runs code · Classify every finding
Compare the diff with the PR title, body and commits
Looks for missing states, missing translations and controls added to only one surface.
Read · Hold the change to its intent
Severity, coverage table and verdict come from it
Output starts with a scope block, then findings with Status, Location, Before, After and Why.
Hand off to better-interface
No checkout, switch or stash
Fetches PR refs into .git and reads files with git show. Rendered checks are opt-in and use an isolated worktree for other targets.
Runs code · Never change the working tree

From the official docs

Permissions

Low risk

The skill runs git and gh commands against your repo and can create a temporary worktree, but SKILL.md bans checkout, switch and stash. Read the commands before approving them.

What it can do

Read your data
Create and change things
Delete things
Read-only modeHow to turn it on

Watch out for

It fetches from your remote and writes refs in .git
scope-resolution.md has it run git fetch (including git fetch origin pull/<n>/head into refs/remotes/pr/<n>), git remote set-head origin --auto and, on shallow clones, git fetch --deepen. It says these write only under .git and are permitted. They use the network. github.com
A rendered review can add a temporary worktree
For targets other than your working tree, SKILL.md suggests git worktree add under /tmp and removing it when done. Rendered checks are opt-in. github.com
It uses the gh CLI when available
Pull request text and status come from gh. SKILL.md says any gh failure is treated as no pull request found. github.com
The plugin route installs 14 skills
The README's Claude Code plugin (interfaces, version 1.17.0) installs the whole repo, 14 skills, not just the 8 this one needs. plugin.json lists no hooks or MCP servers. The skills CLI command in the install box installs only the 8. github.com

Technical details

Turning on read-only	SKILL.md states a change review is read-only, including the checkout.
Talks to	git remote (git fetch). GitHub (gh pr view, gh pr status)
Scopes	your git repo GitHub via gh (pull requests)

Questions

What does the interface-review skill do?

It reviews the interface impact of a branch, pull request or uncommitted change, and labels each finding Introduced, Regression or Pre-existing. It then hands the report to better-interface for severity and a verdict.

How do I install and run it?

Use the install box above, which installs interface-review together with better-interface and the six better-* skills it depends on. Then run /interface-review, optionally followed by a target such as pr 482.

Why does it not run automatically?

Its frontmatter sets disable-model-invocation: true, and better-interface says it is user-invoked and cannot be started from another skill. You must type the command.

Does it work in the Claude app?

The README documents a Claude Code plugin and the skills CLI, not an upload to the Claude app. Its steps use git and, for pull requests, the gh CLI.

Is it safe to install?

SKILL.md says a change review is read-only for your checkout and bans checkout, switch and stash. It does run git and gh commands, fetches PR refs into .git, and can add a temporary worktree under /tmp for a rendered review, so check commands you approve.

How is it different from better-interface?

better-interface reviews a screen, flow or whole interface. interface-review reviews a change, resolves its scope and sends the findings to better-interface. The second does not work without the first.

Information

updated Nov 2, 2026

Repository: jakubkrehel/skills
Folder: skills/interface-review

jakubkrehel/skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6

jakubkrehel/skills README · github.com
interfaces plugin.json · github.com
interface-review SKILL.md · github.com
better-interface SKILL.md · github.com
interface-review scope-resolution.md · github.com
interface-review removed-signals.md · github.com