What problem does it solve? Reviewing frontend pull requests requires checking many distinct concerns—design-system usage, accessibility, state handling, performance, security, and test coverage—which a single generic review pass often misses or covers shallowly. ## Core Features & Use Cases - Parallel specialist agents: Spawns up to eight focused review agents (design-system, a11y, ui-state, ui-perf, ui-security, ui-testing, ui-docs, comments) in one batch, each scoped to relevant file categories. - UI gating and file classification: Categorizes changed files into ui-component, ui-style, ui-hook, ui-story, ui-test, and non-ui, and bails out early when a PR contains no UI changes. - Repo conventions loading: Distills repo-specific UI learnings and review heuristics into a single conventions file that agents reference by path, keeping prompts small. - Use Case: Given a GitHub PR touching React components and hooks, run the skill to get a severity-grouped report (BLOCKING / SHOULD-FIX / SUGGESTION) with file:line findings, existing-comment status, and per-lens coverage. ## Quick Start Ask the assistant to review the UI in a pull request by providing its URL or number, for example: review the UI in PR #142.
