Reviews implemented code for security, quality, performance, and test coverage using specialized review agents. Use when task file is in review/ directory and requires comprehensive code review before approval. Launches test-coverage-analyzer, error-handling-reviewer, and security-reviewer in parallel.
/plugin marketplace add dhruvbaldawa/ccconfigs/plugin install experimental@ccconfigsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Given task file path .plans/<project>/review/NNN-task.md:
Initial Review:
git diff on Files listedSpecialized Review (Parallel Agents): Launch 3 review agents in parallel for deep analysis:
Agents run in separate contexts and return scored findings.
Consolidate Findings:
Decide - APPROVE or REJECT:
Update task status using Edit tool:
**Status:** [current status] → Replace **Status:** APPROVED**Status:** [current status] → Replace **Status:** REJECTEDAppend notes (see formats below) - include agent findings
Report completion
| Area | Check |
|---|---|
| Security | Input validation, auth checks, secrets in env, rate limiting, SQL parameterized |
| Quality | Readable, no duplication, error handling, follows patterns, diff <500 lines |
| Performance | No N+1 queries, efficient algorithms, proper indexing |
| Tests | Covers Validation, behavior-focused, edge cases, error paths, suite passing |
After initial review, invoke agents in parallel using the Task tool with subagent_type="general-purpose":
Launch all three agents simultaneously using Task tool:
Task(
description: "Analyze test coverage",
prompt: "You are test-coverage-analyzer. Analyze test coverage for:
Task file: [task_file_path]
Test files: [list test files]
Implementation files: [list impl files]
[Include full agent prompt from experimental/agents/review/test-coverage-analyzer.md]",
subagent_type: "general-purpose"
)
Task(
description: "Review error handling",
prompt: "You are error-handling-reviewer. Review error handling in:
Task file: [task_file_path]
Implementation files: [list impl files]
[Include full agent prompt from experimental/agents/review/error-handling-reviewer.md]",
subagent_type: "general-purpose"
)
Task(
description: "Security review",
prompt: "You are security-reviewer. Review security in:
Task file: [task_file_path]
Implementation files: [list impl files]
[Include full agent prompt from experimental/agents/review/security-reviewer.md]",
subagent_type: "general-purpose"
)
Call all three Task invocations in a single message to run them in parallel.
Each agent returns:
Consolidate findings using the confidence/severity mappings from Process step 3.
**review:**
Security: 90/100 | Quality: 95/100 | Performance: 95/100 | Tests: 90/100
Working Result verified: ✓ [description]
Validation: 4/4 passing
Full test suite: [M]/[M] passing
Diff: [N] lines
**Specialized Review Findings:**
- Test Coverage: No CRITICAL gaps (0 gaps rated 9-10)
- Error Handling: 1 HIGH finding - [description with justification why acceptable]
- Security: No vulnerabilities detected (0 findings >70 confidence)
APPROVED → testing
**review:**
Security: 65/100 | Quality: 85/100 | Performance: 90/100 | Tests: 75/100
**Specialized Review Findings:**
CRITICAL Issues (must fix):
1. [Security/Test/Error] - [Description from agent] - [Confidence/Severity/Criticality score]
2. [Security/Test/Error] - [Description from agent] - [Confidence/Severity/Criticality score]
HIGH Issues (review recommended):
1. [Security/Test/Error] - [Description from agent] - [Confidence/Severity/Criticality score]
REJECTED - Blocking issues:
1. [Specific issue + fix needed]
2. [Specific issue + fix needed]
Required actions:
- [Action 1 - address CRITICAL findings]
- [Action 2 - address blocking issues]
- [Action 3 - consider HIGH findings]
REJECTED → implementation
Must REJECT if any:
Can APPROVE with HIGH findings if:
When review is complete (status updated to APPROVED or REJECTED):
✅ Review complete. Status: [STATUS]This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.