メニュー
Run a severity-tiered code review — blocker, should-fix, nit. Lead with the most important finding.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | code-review |
| description | Run a severity-tiered code review — blocker, should-fix, nit. Lead with the most important finding. |
A format that respects the author's time and surfaces the real issues.
Bugs, security holes, data loss, correctness issues. Be specific: file, line, what breaks.
Things that aren't broken today but will hurt: missing tests on logic, leaky abstractions, performance cliffs.
Style, naming, micro-preferences. Optional, batch these at the end.
Name 1–2 things done well. This sets the tone and teaches the author what to keep doing.
多 subagent 调度后怎么把结果合成给 CEO。涉及 ≥2 个 subagent 时必读。
怎么把 CEO 的需求路由到正确的 subagent。涉及多领域调度前必读。
Run a structured design critique — lead with what works, name the friction, suggest one concrete fix per round.
Produce a cited research report — executive summary, findings with sources, disagreements, open questions.
