メニュー
Review uncommitted git changes for bugs/regressions via Codex MCP and present a structured report. Use when asked to review local changes or find bugs in current work. Requires Codex MCP to be configured.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when reviewing code for bugs with finder, challenger, and referee roles, especially when independent review is needed to reduce false positives.
Optimize an agent skill through bounded repeated trials, binary evaluations, targeted prompt mutations, and auditable keep/discard decisions. Use when asked to optimize, benchmark, evaluate, or systematically improve an existing skill. Produces an improved candidate skill, run artifacts, a results log, and a mutation changelog without overwriting the original.
Organize raw project documentation into a focused, cross-linked docs/ structure with an adaptive INDEX.md and a recommended AGENTS.md entry point. Preserve the source's natural document types; create stories only when they already exist and incremental slices only when the user wants them. Use when starting from raw documentation or restructuring scattered project docs.
Record one web application feature flow as a compact GIF using an existing Playwright installation. Use when the user asks for a visual demo, changelog artifact, documentation asset, or pull-request evidence. Creates local capture artifacts first; installation, publication, commits, uploads, and pull-request edits always require separate approval.
Coordinate specialized agent roles across complex tasks using dependency-aware planning, explicit ownership, structured handoffs, safe integration, and evidence-based quality gates. Use when work has multiple independent streams or genuinely benefits from isolated expertise; fall back transparently when the runtime cannot provide separate workers.
Draft and, after approval, capture an observed reusable lesson in an existing skill's gotchas.md. Use after a verified bug, architecture error, process failure, or misunderstanding when the lesson can be generalized without exposing project or user information.
| name | codex-review |
| description | Review uncommitted git changes for bugs/regressions via Codex MCP and present a structured report. Use when asked to review local changes or find bugs in current work. Requires Codex MCP to be configured. |
| version | 1.0.1 |
| level | advanced |
| category | code-quality |
Delegates code review of uncommitted changes to Codex MCP, presents a structured report, and helps the user plan fixes. Three phases, executed in order.
gotchas.md before startingRead references/codex-prompt.md for the full prompt template and scope clause substitution rules.
Call mcp__codex__codex exactly once with these parameters:
| Parameter | Value |
|---|---|
sandbox | "read-only" |
approval-policy | "never" |
prompt | From references/codex-prompt.md, with {{SCOPE_CLAUSE}} replaced |
See references/json-schema.md for the output contract and validation rules. The raw report template is at templates/output-schema.json.
If the MCP call fails, times out, or is unavailable, report the exact failure and stop. Do not fabricate findings or silently substitute a different review method.
Read references/presentation-format.md for the display format. See examples/ for concrete output samples.
Before presenting findings:
references/json-schema.md.UNVERIFIED EVIDENCE in the presentation.If findings is empty: say "No issues found in the reviewed scope." Show any skipped files, out_of_scope entries, or checks that were not run, then stop — do not proceed to Phase 3.
Ask the user which finding IDs they want to fix:
"Which issues would you like me to fix? You can list IDs (e.g., REV-001, REV-003) or say 'all'."
CRITICAL — next turn action: When the user replies with their selection, your very first tool call MUST be EnterPlanMode. Do not output any text or call any other tool before entering plan mode. The plan you write must: