メニュー
Comprehensive multi-agent code review with parallel analysis. Use for thorough code reviews, finding bugs, checking regressions, or getting alternative implementation perspectives.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | code-review |
| description | Comprehensive multi-agent code review with parallel analysis. Use for thorough code reviews, finding bugs, checking regressions, or getting alternative implementation perspectives. |
| context | fork |
Orchestrate parallel sub-agent reviews for comprehensive code analysis and actionable feedback.
Identify what to review:
# Option A: Recent changes
git diff HEAD~1
# Option B: Staged changes
git diff --staged
# Option C: Specific commit range
git log --oneline -10 # then select range
# Option D: Current working state
git status
Deploy parallel sub-agents with focused tasks:
| Sub-Agent | Task |
|---|---|
| Spec Reviewer | Check implementation against UPP-1.3.spec.md and compliance requirements |
| Standards Reviewer | Compare against existing provider patterns and org coding standards |
| Bug Hunter | Search for regressions, edge cases, error handling gaps |
| API Validator | Web search to verify API/library usage correctness |
Prompt each sub-agent with:
"Perform a comprehensive code review of [scope]. Investigate spec compliance, coding standards consistency, and validate any API/library usage against current documentation. Report findings as actionable items."
Aggregate sub-agent reports into:
# Code Review Report
## Files Reviewed
- `path/to/file1.ts`
- `path/to/file2.ts`
## Critical Issues 🔴
| File | Line | Issue | Fix |
|------|------|-------|-----|
## Recommendations 🟡
| File | Line | Suggestion | Rationale |
|------|------|------------|-----------|
## Alternative Perspectives 🔵
[Alternative implementation approaches from sub-agents]
## Regression Analysis
| Risk | Affected Area | Resolution Plan |
|------|---------------|-----------------|
## Action Items
- [ ] Fix: [critical item]
- [ ] Consider: [recommendation]
- [ ] Verify: [needs validation]
Update llms.md documentation for LLM consumption based on codebase changes. Use when adding providers, changing APIs, updating types, or when the LLM reference guide drifts from implementation.
Update and reorganize README documentation based on codebase changes. Use when adding features, refactoring modules, updating APIs, or when documentation drifts from implementation.
Generate structured changelogs for app releases from git history. Use when preparing releases, documenting changes, or creating version notes.
Review feature implementations for spec compliance, code quality, and organizational consistency. Use when implementing features, checking spec compliance, validating API implementations, or preparing releases.