원클릭으로
review
Use after verify passes - runs 5 rounds of self-review against the plan/spec, fixing issues found in each round
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use after verify passes - runs 5 rounds of self-review against the plan/spec, fixing issues found in each round
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | review |
| description | Use after verify passes - runs 5 rounds of self-review against the plan/spec, fixing issues found in each round |
5-round self-review cycle. Each round examines the implementation against the plan and spec, identifies issues, fixes them, and re-verifies.
Review all changes against:
Completeness:
Correctness:
Scope:
Security (OWASP Top 10):
Tests:
If any issues are found:
If a round finds no issues, note it and continue to the next round. Even if round 3 is clean, still run rounds 4 and 5 - fresh eyes catch different things.
Report summary:
If all 5 rounds pass clean or all issues were resolved, the review is complete. Hand control back to pick-issue for PR creation.
Use when ready to implement - selects a GitHub Issue, creates worktree, implements with TDD, verifies, reviews 5x, and creates PR. Numeric argument (e.g. pick-issue 3) is the issue number, not a parallelism count.
Use when you want to be exhaustively questioned about a plan or design until shared understanding is reached - asks one question at a time, traverses the design tree, and proposes a recommended answer for each question
Use to delegate all hands-on work to Codex - plan-writing, implementation, and refactoring. Opus reads, thinks, reviews, and writes docs only.
Use after a PR is opened and you want it merged - waits for CI to pass, marks draft PRs ready, removes the worktree, then merges and cleans up
Use when starting new feature work, adding functionality, or modifying behavior - explores design before implementation, creates plan, PR, and GitHub Issues
Use when encountering test failures, bugs, or unexpected behavior - requires root cause investigation before any fix attempt