Menú
Use before claiming work is done, fixed, passing, complete, or ready to merge.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when waiting for servers, jobs, files, tests, queues, or external processes.
Use when a bounded subtask is summarization, mechanical review, fixture inspection, proposal triage, verification, or boilerplate.
Use when locating where a symbol, function, type, command, or constant is defined or referenced, instead of grep/find/read chains.
Use when tempted to add broad abstractions, future-proofing, or extra product surface beyond the requested change.
Use before asking the user about infrastructure, preferences, conventions, prior decisions, or past incidents.
Use when evaluating reviewer feedback, review delegates, or suggested code changes.
| name | verification-before-completion |
| description | Use before claiming work is done, fixed, passing, complete, or ready to merge. |
| source | bundled |
Completion claims require fresh evidence from this work session.
Before saying a task is done:
Avoid "should work", "looks good", or "probably fixed" when no verification ran. If verification is too expensive or blocked, say that directly and explain the residual risk.
