ワンクリックで
requesting-code-review
Get a fresh-eyes review of your own change before calling it done
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Get a fresh-eyes review of your own change before calling it done
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags
Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done
Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable
Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed
Author or connect a Model Context Protocol server so an agent gains new tools
Build automated pipelines that gate merges and ship reliably
| name | requesting-code-review |
| description | Get a fresh-eyes review of your own change before calling it done |
| version | 1 |
| trust | built-in |
You are biased toward your own work — you test what you built, not what's required. A fresh-eyes pass catches what you can't see. Do this before finalizing anything non-trivial.
git diff is clean, tests pass.Agent
tool) and give it ONLY: the diff, the original requirement, and the instruction
to review for correctness, edge cases, security, missing tests, and clarity —
and to try to REFUTE that the change is correct. Don't tell it your conclusions.