devteam-review
npx machina-cli add skill michael-harris/devteam/devteam-review --openclawCurrent session: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_current_session 2>/dev/null || echo "No active session"
Active sprint: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_kv_state "active_sprint" 2>/dev/null || echo "None"
Failure count: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_kv_state "consecutive_failures" 2>/dev/null || echo "0"
DevTeam Review Command
Command: /devteam:review [target] [options]
Run a coordinated code review across multiple reviewers. Launches the Code Review Coordinator to orchestrate language-specific and domain-specific reviewers.
Usage
# Review current changes (staged + unstaged)
/devteam:review
# Review specific files
/devteam:review "src/api/auth.ts" "src/models/user.ts"
# Review specific scope
/devteam:review --scope "src/api/"
# Review with specific focus
/devteam:review --focus security
/devteam:review --focus performance
/devteam:review --focus architecture
# Review a PR
/devteam:review --pr 42
Options
| Option | Description |
|---|---|
--scope <path> | Limit review to specific files/directories |
--focus <area> | Focus on: security, performance, architecture, correctness, all |
--pr <number> | Review a specific pull request |
--severity <level> | Minimum severity to report: critical, warning, info |
--eco | Cost-optimized execution |
Your Process
Phase 0: Initialize Session
source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh"
source "${CLAUDE_PLUGIN_ROOT}/scripts/events.sh"
SESSION_ID=$(start_session "/devteam:review $*" "review")
log_session_started "/devteam:review $*" "review"
Phase 1: Launch Code Review Coordinator
Delegate to the orchestration:code-review-coordinator agent, which will:
- Detect languages and frameworks in the target files
- Select appropriate language-specific code reviewers
- Run database reviewers if schema changes are detected
- Aggregate findings across all reviewers
- Produce a unified review report with severity ratings
const result = await Task({
subagent_type: "orchestration:code-review-coordinator",
prompt: `Code review request:
Target: ${target || 'current changes'}
Scope: ${scope || 'auto-detect'}
Focus: ${focus || 'all'}
Coordinate reviewers to check:
1. Code correctness and logic errors
2. Security vulnerabilities
3. Performance issues
4. Code style and best practices
5. Test coverage gaps
6. Documentation needs`
})
Phase 2: Report
Output a review report showing:
- Summary of findings by severity
- File-by-file review comments
- Recommended changes
- Overall code quality assessment
See Also
/devteam:implement- Implement review feedback/devteam:bug- Fix bugs found during review/devteam:test- Run tests to verify fixes
Source
git clone https://github.com/michael-harris/devteam/blob/main/skills/devteam-review/SKILL.mdView on GitHub Overview
devteam-review runs a unified code review across multiple reviewers by launching the Code Review Coordinator. It orchestrates language-specific and domain-specific reviewers, aggregates findings, and delivers a unified report with severity ratings to guide fixes.
How This Skill Works
The process starts with initializing a review session, then Phase 1 delegates to the orchestration to detect languages/frameworks, assign reviewers, and collect findings. The Code Review Coordinator aggregates results across all reviewers and produces a unified report with severity ratings, followed by Phase 2 where you review file-by-file comments and recommended changes.
When to Use It
- Review the current changes (staged and unstaged) with a single, coordinated pass.
- Review specific files, e.g., /devteam:review "src/api/auth.ts" "src/models/user.ts".
- Limit the review to a scope using --scope to focus on a directory or file set.
- Focus on a domain area like security, performance, or architecture to guide reviewers.
- Review a pull request using --pr <number> to target a specific PR.
Quick Start
- Step 1: Run /devteam:review [target] [options] to start the coordinated review.
- Step 2: Let the Code Review Coordinator detect languages, assign reviewers, and compile findings.
- Step 3: Review the Phase 2 report and implement changes as recommended.
Best Practices
- Define scope before starting: use --scope to limit the review to relevant paths.
- Choose a clear focus: security, performance, or architecture to guide reviewers.
- Anchor the review on a specific PR when possible with --pr <number>.
- Initialize the review session properly so the Code Review Coordinator can orchestrate reviewers.
- Review the unified Phase 2 report and implement changes using the appropriate devteam commands.
Example Use Cases
- Review current changes (staged + unstaged) across multiple files with a single coordinated pass.
- Review specific files like src/api/auth.ts and src/models/user.ts.
- Limit the review to a scope such as src/api/.
- Focus on security during a review of authentication and authorization code.
- Review PR #42 and generate a unified report with severity ratings.
