ワンクリックで
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when you have a written implementation plan and need to execute it directly in the current session on main/master
Use when implementation is complete to verify and finalize work directly on main/master
Use when implementing small or low-complexity changes with minimal ceremony — modular, domain-centered behavior, clear separation from infrastructure, and practical SOLID guardrails without full hex/DDD layering
Use before writing an implementation plan — recommend lightweight vs heavyweight (hex-infra, DDD depth) from signals, confirm with the user, and record the decision for execution
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Use when you have a spec or requirements for a multi-step task, before touching code
| name | requesting-code-review |
| description | Use when completing tasks, implementing major features, or before merging to verify work meets requirements |
Run a structured in-session review to catch issues before they cascade.
Core principle: Review early, review often.
Mandatory:
Optional but valuable:
1. Gather review scope:
git status
git diff
2. Review against requirements:
Check:
3. Act on findings:
Review checklist:
Action:
Subagent-Driven Development:
Executing Plans:
Ad-Hoc Development:
Never:
If reviewer wrong:
Use the checklist above for every review pass.