orchestrate-review
A systematic review tool that performs multi-pass audits on code for security, quality, and coverage.
Install
mkdir -p .claude/skills/orchestrate-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6218" && unzip -o skill.zip -d .claude/skills/orchestrate-review && rm skill.zipInstalls to .claude/skills/orchestrate-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when user asks to \"deep review the code\", \"thorough code review\", \"multi-pass review\", or when orchestrating the Phase 9 review loop. Provides review pass definitions (code quality, security, performance, test coverage), signal detection patterns, and iteration algorithms.Key capabilities
- →Orchestrate multi-pass code reviews
- →Detect signals for database, API, and frontend changes
- →Aggregate findings by severity
- →Iterate through fixes until clean
- →Perform stall detection during review loops
How it works
The skill spawns parallel task agents to perform specific review passes based on detected file signals. It then aggregates findings, applies fixes via the Edit tool, and iterates until the code is clean or a stall is detected.
Inputs & outputs
When to use orchestrate-review
- →Perform deep code security analysis
- →Review code for performance bottlenecks
- →Check test coverage and quality standards
- →Verify multi-pass architectural compliance
About orchestrate-review
Provides structured review passes including code quality, security audits, performance checks, and test coverage analysis. It is designed for deep, multi-dimensional evaluation of codebase changes.
Use when user asks to "deep review the code", "thorough code review", "multi-pass review", or when orchestrating Phase 9 review loop. Provides review pass definitions (code quality, security, performance, test coverage, specialists), signal detection patterns, and iteration algorithms.
When not to use it
- →When the user has not requested a deep or multi-pass review
Prerequisites
Limitations
- →Maximum of 5 iterations per review loop
- →Stalls after 1 consecutive identical-hash iteration
- →Requires manual intervention for critical or high-severity security fixes
How it compares
Unlike manual review, this skill automates the entire loop of detection, aggregation, fix application, and verification across multiple specialized domains.
Compared to similar skills
orchestrate-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| orchestrate-review (this skill) | 1 | 8mo | Review | Advanced |
| github-code-review | 13 | 6mo | Review | Advanced |
| reviewing-nextjs-16-patterns | 11 | 12mo | Review | Intermediate |
| agent-code-analyzer | 3 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by avifenesh
View all by avifenesh →You might also like
github-code-review
ruvnet
Comprehensive GitHub code review with AI-powered swarm coordination
reviewing-nextjs-16-patterns
djankies
Review code for Next.js 16 compliance - security patterns, caching, breaking changes. Use when reviewing Next.js code, preparing for migration, or auditing for violations.
agent-code-analyzer
ruvnet
Agent skill for code-analyzer - invoke with $agent-code-analyzer
code-review-ai-ai-review
sickn33
You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C
code-review-developer
anyproto
Context-aware routing to code review guidelines. Use when reviewing pull requests, providing code feedback, or discussing review standards.
codex-code-review
tyrchen
Perform comprehensive code reviews using OpenAI Codex CLI. This skill should be used when users request code reviews, want to analyze diffs/PRs, need security audits, performance analysis, or want automated code quality feedback. Supports reviewing staged changes, specific files, entire directories, or git diffs.