Menu
Use when claiming work is done, fixed, passing, ready, reviewed, committed, or safe to merge.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when preparing local changes, a branch, pull request, merge request, or merge-to-main for final review before publishing, opening a PR, merging, or claiming readiness.
Use when implementing any feature, bugfix, behavior change, or refactor before writing production code.
Use when the user asks to shape fuzzy planning, product/design/engineering tradeoffs, scope/spec/ticket plans, or says "challenge this/help me think"; delegate to an advisor subagent. Good for rough ideas, second opinions, load-bearing decisions, or scope cuts. Skip scoped implementation, narrow bugs, reviews, and "just build" requests.
Use when setting up a project-local eval harness for prompts, agents, judges, RAG, tools, or other LLM behavior, especially when the default should be free/OSS promptfoo with repo-owned artifacts.
Use when a pull request or merge request needs to be driven to merge — watching CI, responding to review feedback, and merging once green and approved, across GitHub, Forgejo, or GitLab.
Use when the user wants repository task tracking, shared agent task state, cross-worktree coordination, tiber setup/install/scaffold guidance, or task create/list/show/prioritize/validate/close workflows. Plugin install and session start are non-mutating; setup integration starts with dry-run previews.
| name | verification-before-completion |
| description | Use when claiming work is done, fixed, passing, ready, reviewed, committed, or safe to merge. |
Evidence comes before claims. A completion statement is only valid when fresh verification proves the exact scope being claimed.
| Claim | Required evidence |
|---|---|
| "Tests pass" | Fresh full relevant test output with zero failures |
| "Lint/format is clean" | Fresh lint/format command output |
| "Bug fixed" | The original symptom or regression test now passes |
| "Requirement met" | Requirement-by-requirement check against files, output, runtime state, or PR state |
| "Ready to merge" | Current checks, review state, branch status, and required approvals |
Partial checks prove partial claims only. A focused test can prove a narrow fix; it cannot prove the whole repo is green.
When evidence is missing, say what was checked and what remains unverified.
