Code Review

Trigger Conditions

• User requests a code review
• User mentions keywords such as "code review", "代码审查", "审查代码"
• User requests checks for security, performance, or code quality

Steps

Step 1: Organize User Requirements

• Review target (e.g., "current git staged changes", "src/auth/ directory", "PR #42")
• Focus areas (security/performance/quality; no restriction if not specified by the user)
• Additional requirements provided by the user

Step 2: Launch Review Subagent

code-reviewer.md

• description

  : "In-depth Code Review"

• prompt

  : Full content of

  code-reviewer.md

  + "\n\n## Review Task\n" + User requirement instructions

• model

  : Determined by the

  model

  field in the frontmatter of

  code-reviewer.md

  (default to sonnet if not specified)

• Do not collect code content in the main agent, only pass the description of the review target
• The subagent has its own tools like Bash and Read, and will read code and diffs on its own
• Must pass the entire content of

  code-reviewer.md

  to the subagent; do not truncate or summarize

Step 3: Output Review Results