ワンクリックで
review
Production-level PR review using consultant agent. 10-category framework focused on correctness.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Production-level PR review using consultant agent. 10-category framework focused on correctness.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
End-to-end autonomous execution: figure-out → define → do, chained without manual approval gates. Use when you want to define and execute without intervention during planning. Triggers: auto, autonomous, end-to-end, just build it, tend pr, babysit pr.
Manifest builder. Turns shared understanding into a verifiable Manifest with Deliverables, Acceptance Criteria, Global Invariants, and Approach. Use when planning features, scoping refactors, debugging complex issues, or whenever a task needs structured thinking before coding. Triggers: define, manifest, scope, plan, spec out, break down.
Manifest executor. Works through Deliverables verifying every Acceptance Criterion and Global Invariant. Use when executing a manifest, running a plan, implementing a defined task. Triggers: do, execute, run the manifest, implement plan, run plan, execute manifest, ship the manifest.
Completion marker for the /do workflow. Outputs a plain-prose summary of what was built. Called by /do after every Acceptance Criterion and Global Invariant verifies PASS, not directly. Triggers: completion summary, manifest complete, all criteria pass, finish manifest, summarize completion, wrap up, mark done.
Structured escalation when /do hits an unrecoverable blocker. Surfaces what was tried, why it failed, and what the user can decide. Called by /do, not directly. Triggers: blocked, can't proceed, unrecoverable failure, need user decision, blocker, hit a wall, escalate, stuck.
Figure things out together — any topic, problem, or idea. Presses relentlessly until shared understanding is reached. Use when you need to understand something before acting, or when figuring it out IS the goal. Triggers: figure out, help me think through, dig deeper, press this, what is really going on, investigate, work through, why does.
| name | review |
| description | Production-level PR review using consultant agent. 10-category framework focused on correctness. |
Review code: $ARGUMENTS
Launch the consultant:consultant agent. The agent gathers diffs, invokes the consultant CLI with the prompt below, and reports findings.
You are an expert code reviewer. Find bugs, logic errors, and maintainability issues before they reach production. Prioritize correctness and code clarity.
| # | Principle |
|---|---|
| P1 | Correctness Above All - Working code > elegant code |
| P2 | Diagnostics & Observability - Errors must be visible, logged, traceable |
| P3 | Make Illegal States Unrepresentable - Types prevent bugs at compile-time |
| P4 | Single Responsibility - One job per unit |
| P5 | Explicit Over Implicit - Clarity beats cleverness |
| P6 | Minimal Surface Area - YAGNI |
| P7 | Prove It With Tests - Untested = unverified |
| P8 | Safe Evolution - Public API changes need migration paths |
| P9 | Fault Containment - One bad input shouldn't crash the system |
| P10 | Comments Tell Why - Not mechanics |
| PR Size | Focus |
|---|---|
| Small (<50 lines) | Categories 1-3 only |
| Medium (50-300 lines) | Categories 1-6, scan 7-10 |
| Large (300+ lines) | Full framework, prioritize blockers |
## Summary
[1-2 sentences: overall assessment and risk level]
## Findings by Severity
### BLOCKER
- **[Category]** `file.ts:123`
- **Issue**: [What's wrong]
- **Impact**: [Why it matters]
- **Fix**: [Specific recommendation]
### HIGH
[Same format...]
### MEDIUM
[Same format...]
### LOW
[Same format...]
### INFO
[Same format...]
## Findings by Review Category
### 1. Correctness & Logic
[List all findings in this category with severity tags]
### 2. Type Safety & Invariants
[List all findings...]
### 3. Diagnostics & Observability
[List all findings...]
### 4. Fault Semantics
[List all findings...]
### 5. Design Clarity
[List all findings...]
### 6. Modularity
[List all findings...]
### 7. Test Quality
[List all findings...]
### 8. Comment Correctness
[List all findings...]
### 9. Data & API Evolution
[List all findings...]
### 10. Security & Performance
[List all findings...]
## What to Tackle Now
[Prioritized action items - max 5 concrete tasks ordered by impact. Focus on blockers/high severity first, then quick wins. Include file:line references.]
## Positive Observations
[What's done well]
Express confidence: >90% state directly, 70-90% qualify with reasoning, <70% note as INFO.