원클릭으로
verify
Use before claiming work is complete - requires running verification commands and presenting evidence of success
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use before claiming work is complete - requires running verification commands and presenting evidence of success
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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
| name | verify |
| description | Use before claiming work is complete - requires running verification commands and presenting evidence of success |
Evidence before claims. Never say "done" without proof.
Rule: No success claims without running commands and showing output.
Before stating that anything works:
| Claim | Required Evidence |
|---|---|
| "Tests pass" | Test output showing 0 failures + exit code 0 |
| "Lint clean" | Linter output showing 0 errors + exit code 0 |
| "Build succeeds" | Build output + exit code 0 |
| "Bug is fixed" | Test for the original bug passes |
| "All requirements met" | Line-by-line checklist against spec |
| Language | Tests | Lint | Build |
|---|---|---|---|
| Rust | cargo test | cargo clippy | cargo build |
| Go | go test ./... | golangci-lint run | go build ./... |
| Ruby | bundle exec rspec | bundle exec rubocop | - |
| TypeScript | npx vitest run / npx jest | npx eslint . | npx tsc --noEmit |
Detect the project's actual setup.
These phrases indicate a claim without evidence:
If verification fails, do not claim partial success. Invoke the debugging skill and fix the issue. Re-verify from scratch after the fix.