[GIT] PR review with parallel specialized agents. Use when reviewing pull requests or code.
Conducts comprehensive pull request reviews using parallel specialized agents for security, quality, and architecture.
/plugin marketplace add yonatangross/orchestkit/plugin install ork-workflows@orchestkitDeep code review using 6-7 parallel specialized agents.
/review-pr 123
/review-pr feature-branch
BEFORE creating tasks, clarify review focus:
AskUserQuestion(
questions=[{
"question": "What type of review do you need?",
"header": "Focus",
"options": [
{"label": "Full review (Recommended)", "description": "Security + code quality + tests + architecture"},
{"label": "Security focus", "description": "Prioritize security vulnerabilities"},
{"label": "Performance focus", "description": "Focus on performance implications"},
{"label": "Quick review", "description": "High-level review, skip deep analysis"}
],
"multiSelect": false
}]
)
Based on answer, adjust workflow:
BEFORE doing ANYTHING else, create tasks to track progress:
# 1. Create main review task IMMEDIATELY
TaskCreate(
subject="Review PR #{number}",
description="Comprehensive code review with parallel agents",
activeForm="Reviewing PR #{number}"
)
# 2. Create subtasks for each phase
TaskCreate(subject="Gather PR information", activeForm="Gathering PR information")
TaskCreate(subject="Launch review agents", activeForm="Dispatching review agents")
TaskCreate(subject="Run validation checks", activeForm="Running validation checks")
TaskCreate(subject="Synthesize review", activeForm="Synthesizing review")
TaskCreate(subject="Submit review", activeForm="Submitting review")
# 3. Update status as you progress
TaskUpdate(taskId="2", status="in_progress") # When starting
TaskUpdate(taskId="2", status="completed") # When done
# Get PR details
gh pr view $ARGUMENTS --json title,body,files,additions,deletions,commits,author
# View the diff
gh pr diff $ARGUMENTS
# Check CI status
gh pr checks $ARGUMENTS
Identify:
CC 2.1.6 auto-discovers skills - no manual loading needed!
Relevant skills activated automatically:
code-review-playbook - Review patterns, conventional commentssecurity-scanning - OWASP, secrets, dependenciestype-safety-validation - Zod, TypeScript strictLaunch SIX specialized reviewers in ONE message with run_in_background: true:
| Agent | Focus Area |
|---|---|
| code-quality-reviewer #1 | Readability, complexity, DRY |
| code-quality-reviewer #2 | Type safety, Zod, Pydantic |
| security-auditor | Security, secrets, injection |
| test-generator | Test coverage, edge cases |
| backend-system-architect | API, async, transactions |
| frontend-ui-developer | React 19, hooks, a11y |
# PARALLEL - All 6 agents in ONE message
Task(
description="Review code quality",
subagent_type="code-quality-reviewer",
prompt="""CODE QUALITY REVIEW for PR $ARGUMENTS
Review code readability and maintainability:
1. Naming conventions and clarity
2. Function/method complexity (cyclomatic < 10)
3. DRY violations and code duplication
4. SOLID principles adherence
SUMMARY: End with: "RESULT: [PASS|WARN|FAIL] - [N] issues: [brief list]"
""",
run_in_background=True
)
Task(
description="Review type safety",
subagent_type="code-quality-reviewer",
prompt="""TYPE SAFETY REVIEW for PR $ARGUMENTS
Review type safety and validation:
1. TypeScript strict mode compliance
2. Zod/Pydantic schema usage
3. No `any` types or type assertions
4. Exhaustive switch/union handling
SUMMARY: End with: "RESULT: [PASS|WARN|FAIL] - [N] type issues: [brief list]"
""",
run_in_background=True
)
Task(
description="Security audit PR",
subagent_type="security-auditor",
prompt="""SECURITY REVIEW for PR $ARGUMENTS
Security audit:
1. Secrets/credentials in code
2. Injection vulnerabilities (SQL, XSS)
3. Authentication/authorization checks
4. Dependency vulnerabilities
SUMMARY: End with: "RESULT: [PASS|WARN|BLOCK] - [N] findings: [severity summary]"
""",
run_in_background=True
)
Task(
description="Review test coverage",
subagent_type="test-generator",
prompt="""TEST COVERAGE REVIEW for PR $ARGUMENTS
Review test quality:
1. Test coverage for changed code
2. Edge cases and error paths tested
3. Meaningful assertions (not just truthy)
4. No flaky tests (timing, external deps)
SUMMARY: End with: "RESULT: [N]% coverage, [M] gaps - [key missing test]"
""",
run_in_background=True
)
Task(
description="Review backend code",
subagent_type="backend-system-architect",
prompt="""BACKEND REVIEW for PR $ARGUMENTS
Review backend code:
1. API design and REST conventions
2. Async/await patterns and error handling
3. Database query efficiency (N+1)
4. Transaction boundaries
SUMMARY: End with: "RESULT: [PASS|WARN|FAIL] - [N] issues: [key concern]"
""",
run_in_background=True
)
Task(
description="Review frontend code",
subagent_type="frontend-ui-developer",
prompt="""FRONTEND REVIEW for PR $ARGUMENTS
Review frontend code:
1. React 19 patterns (hooks, server components)
2. State management correctness
3. Accessibility (a11y) compliance
4. Performance (memoization, lazy loading)
SUMMARY: End with: "RESULT: [PASS|WARN|FAIL] - [N] issues: [key concern]"
""",
run_in_background=True
)
If PR includes AI/ML code, add 7th agent:
Task(
description="Review LLM integration",
subagent_type="llm-integrator",
prompt="""LLM CODE REVIEW for PR $ARGUMENTS
Review AI/LLM integration:
1. Prompt injection prevention
2. Token limit handling
3. Caching strategy
4. Error handling and fallbacks
SUMMARY: End with: "RESULT: [PASS|WARN|FAIL] - [N] LLM issues: [key concern]"
""",
run_in_background=True
)
# Backend
cd backend
poetry run ruff format --check app/
poetry run ruff check app/
poetry run pytest tests/unit/ -v --tb=short
# Frontend
cd frontend
npm run format:check
npm run lint
npm run typecheck
npm run test
Combine all agent feedback into structured report:
# PR Review: #$ARGUMENTS
## Summary
[1-2 sentence overview]
## Code Quality
| Area | Status | Notes |
|------|--------|-------|
| Readability | // | [notes] |
| Type Safety | // | [notes] |
| Test Coverage | // | [X%] |
## Security
| Check | Status |
|-------|--------|
| Secrets | / |
| Input Validation | / |
| Dependencies | / |
## Blockers (Must Fix)
- [if any]
## Suggestions (Non-Blocking)
- [improvements]
# Approve
gh pr review $ARGUMENTS --approve -b "Review message"
# Request changes
gh pr review $ARGUMENTS --request-changes -b "Review message"
The pr-status-enricher hook automatically detects open PRs at session start and sets:
ORCHESTKIT_PR_URL - PR URL for quick referenceORCHESTKIT_PR_STATE - PR state (OPEN, MERGED, CLOSED)After submitting a review, optionally notify the team:
mcp__slack__post_message({
channel: "#dev-reviews",
text: "PR #{number} reviewed: {APPROVE|REQUEST_CHANGES} - {summary}"
})
See slack-integration skill for setup.
Use these prefixes for comments:
praise: - Positive feedbacknitpick: - Minor suggestionsuggestion: - Improvement ideaissue: - Must fixquestion: - Needs clarification