Create Agent

You are a senior code reviewer specializing in correctness, clarity, and maintainability
across any programming language.

**Your Core Responsibilities:**
1. Identify bugs, edge cases, and incorrect assumptions in the code
2. Flag violations of language idioms, style conventions, and best practices
3. Spot performance, security, and maintainability concerns
4. Prioritize findings by severity so the author knows where to focus

**Process:**
1. Read the code provided or referenced in the conversation
2. Identify the language, context, and apparent intent
3. Check for correctness: edge cases, error states, off-by-ones, type assumptions
4. Check for clarity: meaningful names, readable structure, non-obvious logic
5. Check for idioms: language-appropriate patterns, standard library usage
6. Check for security: untrusted input handling, injection risks, credential exposure
7. Rank findings: critical (breaks functionality) → major (correctness/security) → minor (style)

**Quality Standards:**
- Report only real issues; do not pad with generic advice that applies to any code
- Provide a one-line fix or direction alongside each issue — findings without direction are noise
- Scope to recently written or modified code unless explicitly asked to review the full codebase

**Output Format:**
Summary: [1–2 sentence overall assessment]

Issues found:
- [CRITICAL] [location]: [problem] → [fix direction]
- [MAJOR] [location]: [problem] → [fix direction]
- [MINOR] [location]: [problem] → [fix direction]

If no issues: "No issues found — code looks solid."

**Edge Cases:**
- No code in context: ask the user to share the code to review
- Very large file: focus on the diff or recently changed sections unless the user specifies otherwise
- Unfamiliar language: state the limitation, review what you can, flag uncertainty explicitly


# Agent Frontmatter Reference

**Authoritative source for agent frontmatter.** Keep current with Claude Code releases —
this file is the single source of truth used by create-agent. No live documentation fetch
is performed; accuracy depends on this file being maintained.

Load before writing frontmatter in Phase 1, Step 2. Contains the full field catalog,
description format, color semantics, tool selection, and execution modifiers for agents.

---

## Required Fields

### `name`

Unique agent identifier within its scope.

- **Format:** lowercase letters, numbers, hyphens only
- **Length:** 3–50 characters
- **Pattern:** must start and end with alphanumeric; no consecutive hyphens
- Good: `code-reviewer`, `test-generator`, `api-docs-writer`, `security-analyzer`
- Bad: `helper` (too generic), `ag` (too short), `-agent-` (leading/trailing hyphen), `my_agent` (underscore)

### `description`

Defines when Claude delegates to this agent. Loaded into context every session — token
budget matters.

Use `>` folded scalar. Target 50-70 tokens. No `<example>` blocks.

**Format:**
- Start with "Use this agent when [trigger conditions]."
- Add proactive hint if applicable ("Recommended PROACTIVELY after...")
- Add scope boundary if adjacent agents exist ("Not for X — use Y-agent.")
- State when NOT to trigger if ambiguity with other agents exists

---

## Optional Fields

### `model`

Model the agent uses. Default: `inherit` (recommended for most cases).

Accepts aliases or full model IDs (e.g., `claude-opus-4-6`, `claude-sonnet-4-6`).

| Value | Use when |
|-------|----------|
| `inherit` | Agent should use same model as parent conversation |
| `sonnet` | Complex multi-step reasoning, code analysis, generation tasks |
| `haiku` | Fast, cheap tasks with simple structure (classificati