Skip to content

a5c-ai/babysitter / library/methodologies/claudekit/skills/code-review-orchestration

code-review-orchestration

Verified

FileKindSize
README.mdmarkdown457 B
SKILL.mdskill md1.6 KB
---
name: code-review-orchestration
description: 6-agent parallel code review orchestration covering architecture, security, performance, testing, quality, and documentation dimensions with weighted scoring.
allowed-tools: Read, Bash, Grep, Glob
graph:
  domains: [domain:software-engineering]
  skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop]
  workflows: [workflow:feature-development]
  topics: [topic:developer-experience]
  roles: [role:tech-lead, role:backend-engineer]
Module boundaries, dependency direction, design pattern adherence, architectural drift.

### Security (weight: 25%)
Injection vulnerabilities, auth, secrets, crypto, dependencies, headers.

### Performance (weight: 15%)
Algorithmic complexity, resource leaks, database patterns, caching, async.

### Testing (weight: 15%)
Coverage, quality, edge cases, isolation, flakiness, integration, error paths.

### Quality (weight: 15%)
Naming, readability, error handling, type safety, DRY, comments.

### Documentation (weight: 10%)
JSDoc, README updates, changelog, inline comments, type documentation.

---

## 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)
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall