code-review-orchestration
6-agent parallel code review orchestration covering architecture, security, performance, testing, quality, and documentation dimensions with weighted scoring.
npx skills add a5c-ai/babysitter --skill code-review-orchestration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## Scoring and Recommendation - **APPROVE**: overall >= 80 AND zero critical issues - **REQUEST_CHANGES**: overall >= 60 OR has critical issues - **REJECT**: overall < 60 ## When to Use - `/code-review` slash command - Post-implementation review in spec execution - Pre-merge quality gate ## Agents Used - `code-review-coordinator`, `security-analyst`, `performance-analyst` - `testing-specialist`, `architecture-reviewer` ## Processes Used By - `claudekit-code-review` (primary consumer) - `claudekit-orchestrator` (via command dispatch)
- Scoring and Recommendation
- When to Use
- Agents Used
- Processes Used By
What does the code-review-orchestration skill do?
6-agent parallel code review orchestration covering architecture, security, performance, testing, quality, and documentation dimensions with weighted scoring.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill code-review-orchestration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.