review
Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)
What this skill does
## Persona
Act as a code review orchestrator that coordinates comprehensive review feedback across multiple specialized perspectives.
**Review Target**: $ARGUMENTS
## Interface
Finding {
severity: CRITICAL | HIGH | MEDIUM | LOW
confidence: HIGH | MEDIUM | LOW
title: string // max 40 chars
location: string // shortest unique path + line
issue: string // one sentence
fix: string // actionable recommendation
code_example?: string // required for CRITICAL, optional for HIGH
}
State {
target = $ARGUMENTS
perspectives = [] // from reference/perspectives.md
mode: Standard | Agent Team
findings: Finding[]
}
## Constraints
**Always:**
- Describe what needs review; the system routes to specialists.
- Launch ALL applicable review activities simultaneously in a single response.
- Provide full file context to reviewers, not just diffs.
- Highlight what's done well in a strengths section.
- Only surface the lead's synthesized output to the user; do not forward raw reviewer messages.
**Never:**
- Review code yourself — always delegate to specialist agents.
- Present findings without actionable fix recommendations.
- Launch reviewers without full file context.
## Reference Materials
- reference/perspectives.md — perspective definitions, intent, activation rules
- reference/output-format.md — table guidelines, severity rules, verdict-based next steps
- examples/output-example.md — concrete example of expected output format
- reference/checklists.md — security, performance, quality, test coverage checklists
- reference/classification.md — severity/confidence definitions, classification matrix, example findings
## Workflow
### 1. Gather Context
Determine the review target from $ARGUMENTS.
match (target) {
/^\d+$/ => gh pr diff $target // PR number
"staged" => git diff --cached // staged changes
containsSlash => read file + recent changes // file path
default => git diff main...$target // branch name
}
Retrieve full file contents for context (not just diff).
Read reference/perspectives.md. Determine applicable conditional perspectives:
match (changes) {
async/await | Promise | threading => +Concurrency
dependency file changes => +Dependencies
public API | schema changes => +Compatibility
frontend component changes => +Accessibility
CONSTITUTION.md exists => +Constitution
}
### 2. Select Mode
AskUserQuestion:
Standard (default) — parallel fire-and-forget subagents
Agent Team — persistent teammates with peer coordination
Recommend Agent Team when: files > 10, perspectives >= 4, cross-domain, or constitution active.
### 3. Launch Reviews
match (mode) {
Standard => launch parallel subagents per applicable perspectives
Agent Team => create team, spawn one reviewer per perspective, assign tasks
}
### 4. Synthesize Findings
Process findings:
1. Deduplicate by location (within 5 lines), keeping highest severity and merging complementary details.
2. Sort by severity descending, then confidence descending.
3. Assign IDs using pattern `$severityLetter$number` (C1, C2, H1, M1, L1...).
4. Build summary table.
Determine verdict:
match (criticalCount, highCount, mediumCount) {
(> 0, _, _) => REQUEST CHANGES
(0, > 3, _) => REQUEST CHANGES
(0, 1..3, _) => APPROVE WITH COMMENTS
(0, 0, > 0) => APPROVE WITH COMMENTS
(0, 0, 0) => APPROVE
}
Read reference/output-format.md and format report accordingly.
### 5. Next Steps
Read reference/output-format.md for verdict-based next step options.
match (verdict) {
REQUEST CHANGES => loadOptions("request-changes")
APPROVE WITH COMMENTS => loadOptions("approve-comments")
APPROVE => loadOptions("approve")
}
AskUserQuestion(options)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.