# Review

> Delegate UI code reviews to a subagent. Reviews components, pages, git changes, or specification files using web design guidelines.

- Skill: `mrclrchtr/review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mrclrchtr/review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mrclrchtr/review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mrclrchtr (https://skillmd.com/u/mrclrchtr)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mrclrchtr/review

---


# Web Design Guidelines Review (Subagent)

## Step 1: Determine Target

**With argument:** Use it directly.

**Without argument:** Determine from session context:
- Clear single target (one commit, one file) → use it
- Ambiguous (multiple commits, unclear scope) → ask user via `AskUserQuestion`

**Ask when unclear.** Use `AskUserQuestion` with options:

**Always include:**
- **All session changes** — all commits made in this conversation (if multiple)
- **Whole feature branch** — diff of current branch vs main
- **Last commit (hash)** — most recent commit only
- **Uncommitted changes** — only if they exist

**Add context-specific options** if identifiable:
- Specific component/file discussed in session
- Particular commit mentioned earlier
- Directory being worked on
- Spec/design file referenced

## Step 2: Find Design System Path

Quick glob (don't read):
```
glob: "docs/**/design-system.md"  
glob: "**/DESIGN_SYSTEM.md"
```

## Step 3: Spawn Agent

**Do NOT gather content yourself.** Just pass identifiers — the agent gets the content.

```yaml
tool: Agent
parameters:
  description: "UI review: [target]"
  subagent_type: "web-design-guidelines:ui-reviewer"
  prompt: |
    Review: [TARGET IDENTIFIER - e.g. "commit abc123", "src/Button.tsx", "uncommitted changes"]
    Design system: [PATH or "none"]
    Context: [BRIEF SESSION CONTEXT - what feature, what spec, focus areas]
```

**Don't:**
- Run `git diff` or `git show`
- Read file contents
- Write diffs to temp files

**Do:**
- Pass commit hash, file path, or "uncommitted changes"
- Pass design system path
- Pass brief context (feature name, spec reference, focus areas)

## Step 4: Return findings to user

