interface-review

Reviews uncommitted changes, branches, and pull requests for interface quality regressions.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/agents --skill interface-review-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interface-review
Source: https://github.com/leonardoacosta/agents/tree/main/skills/interface-review
Command: npx skills add https://github.com/leonardoacosta/agents --skill interface-review-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code review of a diff often misses interface regressions because reviewers read only the added lines and the changed files, not the removed lines or the surfaces that consume the change. This Skill turns a change target (working tree, staged changes, branch, or pull request) into a properly scoped interface review with classified findings. ## Core Features & Use Cases - Scope Resolution: Resolves the review target with exact git commands, handling merge bases, fork PR refs, shallow clones, detached HEAD, mid-rebase states, renames, and exclusions of lockfiles, snapshots, and generated output. - Removed-Signal Detection: Reads the - side of every hunk to catch removed accessibility attributes, focus styles, motion preferences, and text, routing each lead to the owning domain skill. - Finding Classification: Statuses every finding as Introduced, Regression, or Pre-existing, confirmed with git blame against the base ref, then hands the review to better-interface for severity, caps, and verdict. - Use Case: Run /interface-review pr 482 to fetch the PR ref without checking it out, expand the changed components to their consumer surfaces, and produce a change-scoped interface review. ## Quick Start Ask the AI to review the interface quality of pull request 482 using the interface-review skill.

Frequently Asked Questions about interface-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request for interface regressions without checking it out?

Fetch the PR head into a remote-tracking ref with git fetch origin pull/<n>/head:refs/remotes/pr/<n>, then diff against the merge base. This works for forks and never touches the working tree, unlike gh pr checkout.

How to review uncommitted changes vs a branch in git?

Use git diff HEAD plus git ls-files --others --exclude-standard for uncommitted work, and git diff merge-base...HEAD for branch commits. When both exist, review them together but report the committed and uncommitted counts separately.

What happens when there is no change to review?

The skill stops and asks rather than falling back to HEAD~1..HEAD. It reports the repository facts, checks for an open PR on the current branch, and offers the last commit, a named target, or a whole-repository audit.

Does this skill check code correctness, tests, or security?

No. It covers interface quality only and names correctness, test, or security concerns once before pointing to the project's general code review. Domain rules belong to the better-* skills such as better-accessibility and better-layout.

Why does the review read the removed lines of a diff?

Regressions are invisible in the post-change state, so the minus side of every hunk is searched for removed aria attributes, focus styles, motion preferences, and text. A removal is only reported after the owning domain skill confirms nothing replaced it.

Which files are excluded from the change scope?

Lockfiles, snapshots, generated output, generated sources, vendored code, and binaries are excluded and named in the scope block. Font files and images referenced by components stay in scope through the code that uses them.