review

Delegate UI code reviews to a subagent against web design guidelines.

8|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/mrclrchtr/skills --skill review-mrclrchtr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/mrclrchtr/skills/tree/main/plugins/web-design-guidelines/skills/review
Command: npx skills add https://github.com/mrclrchtr/skills --skill review-mrclrchtr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegate UI code reviews to a subagent using established web design guidelines, reducing manual review time and ensuring consistency across components, pages, and diffs.

Core Features & Use Cases

  • Delegates UI review tasks to a subagent that assesses components, pages, git changes, or specification files against design guidelines.
  • Use Case: When validating a new UI feature, trigger a subagent review to catch alignment gaps before code review.

Quick Start

Ask the subagent to review the target UI components or changes against the design guidelines.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate UI code reviews against design guidelines?

Automate UI code reviews by delegating the task to a subagent that checks components, pages, or diffs against established web design guidelines. Provide a target identifier and design system path to guide the review focus.

Can I review uncommitted changes or a specific git commit for UI alignment?

Yes, you can review uncommitted changes or a specific git commit. If the scope is unclear, you will be prompted to select from options like all session changes, whole feature branch, last commit, or uncommitted changes.

What is the best way to catch design guideline gaps before a code review?

The best way to catch alignment gaps is triggering a subagent review of your UI components or changes against your design guidelines. This reduces manual review time and ensures consistency across your project.

Do I need a design system path to review UI components?

Providing a design system path is required when available to ensure the subagent accurately assesses your UI components against the correct web design guidelines during the review process.

What limitations exist when delegating UI reviews to a subagent?

Limitations include the subagent not reading file contents or executing local commands directly. It requires a target identifier like a commit hash or file path and brief session context to guide the review focus.