how-to-code-review
When the user asks for a code review, PR review, or critical look at recent changes, consult this skill to decide whether to delegate to the code-review subagent and how to craft the prompt.
What this skill does
# Handling code review requests Delegate to the `code-review` subagent (Agent tool, `subagent_type: code-review`) instead of reading diffs and writing the review inline. Review runs in a forked Opus context — diff reading, file expansion, and reasoning stay out of the main thread; only the report comes back. ## When to delegate vs. handle inline Delegate when: - The user asks for a code review, PR review, or "look critically" at recent changes. - The user asks "what's wrong with X" or "find issues in Y" about a defined scope. - A natural review point has been reached (just-finished feature, pre-commit check). Handle inline (do not delegate) when: - The user wants a *quick sanity check* on a single small snippet visible in conversation. Delegating costs more than reading three lines. - The user is asking how to fix a *specific known issue*, not asking for issue discovery. - The user wants a discussion or back-and-forth about a design choice — that is conversation, not review. ## Crafting the delegation prompt The subagent's default scope is the working tree against the merge base with main. Override only when the user names something else. Examples: - User: "review my changes" → Delegate with empty prompt. Default scope handles it. - User: "code review the auth refactor" → "Review the auth refactor in the current working tree." - User: "review PR #482" → "Review PR #482." - User: "look at src/api/handlers.go" → "Review src/api/handlers.go." - User: "review the last 3 commits" → "Review the commit range HEAD~3..HEAD." - User: "security-focused review" → "Review the current working tree with emphasis on security (auth, input validation, secret handling, injection)." ## Anti-patterns - Reading the diff yourself and writing the review in the main session. The subagent owns this; doing it inline burns the main context on diff content. - Asking the subagent for full code blocks or diffs in its report. It returns findings keyed to `file:line` — the code is in the working tree. - Delegating mid-discussion before the user has actually asked for review. "Should I refactor X?" is not a review request.
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.