メニュー
Fixes blocking issues identified during code review to achieve APPROVED status. Use when addressing review feedback or resolving blocking bugs. Applies minimal targeted fixes, re-validates, and iterates up to 3 times.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | review-fix |
| description | Fixes blocking issues identified during code review to achieve APPROVED status. Use when addressing review feedback or resolving blocking bugs. Applies minimal targeted fixes, re-validates, and iterates up to 3 times. |
| model | sonnet |
| metadata | {"version":"1.0.0","category":"workflow-automation"} |
Mindset: Get to APPROVED by fixing blocking issues only.
Fix all blocking issues identified in REVIEW.md so the code can ship.
Identify blocking issues:
### Blocking (must fix)
- `src/auth.ts:45` - Missing error handling
- `tests/auth.test.ts` - Test for OAuth failure missing
For each blocking issue:
## Issues
### Blocking (must fix)
- ~~`src/auth.ts:45` - Missing error handling~~ FIXED
- ~~`tests/auth.test.ts` - Test for OAuth failure missing~~ FIXED
### Non-Blocking (nice to have)
- `src/utils.ts` - Consider extracting helper (skipped)
Update with fix iteration count and test results.
DO:
DON'T:
Maximum 3 fix iterations:
If still failing after iteration 3:
REVIEW.md with struck-through fixed issuesSTATUS.md with iteration countBuilds working software by executing implementation plans phase by phase. Use when writing code, running tests, or executing a planned feature build. Implements all phases autonomously, validates each phase, and documents deviations.
Reference skill for security-focused phases (/security, /pentest, /redteam-ai, /harden). Provides OWASP Top 10 checklist, STRIDE threat model, common attack patterns, and exploit classification standards. Load this skill when performing any security audit or generating security-related code reviews.
Creates phased implementation plans with clear scope and acceptance criteria. Use when defining what to build, sequencing work into phases, or establishing validation gates. Produces actionable plans with per-phase validation checklists.
Investigates codebase to find minimum context needed for planning. Use when starting a new feature, analyzing unfamiliar code, or preparing for implementation. Identifies files to touch, patterns to follow, and risks to mitigate.
Reviews code for production readiness with focus on blocking issues. Use when performing quality assurance, verifying implementations, or checking security. Runs automated checks, validates plan compliance, and produces APPROVED or NEEDS_FIX verdict.
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.