Saltar al contenido
TakoAPI
Volver a skills

verify-before-done

por kjaylee

Coding Agents & IDEs
—Aún sin valoraciones
Tu valoración

Resumen

Require fresh verification evidence before claiming work is complete.

Descripción

Qué hace esta skill

Enforces a verification gate before any completion claim, commit, push, PR, or status report. Requires running a fresh command and reading its actual output, exit code, and failure count. Blocks rationalization patterns like 'it should work' or accepting a sub-agent's self-reported success.

It catches the gap between assumption and evidence at the exact moment a false completion claim would otherwise be recorded or communicated.

Cuándo usarla

  • Confirming tests pass before closing a pull request
  • Checking linter output before reporting a clean codebase
  • Validating a bug fix by re-running the original failing test
  • Auditing a sub-agent's 'success' report with an independent command run
  • Ensuring build exit code is 0 before marking a deploy task complete

Flujo de trabajo de ejemplo

ENTRADA

User asks: verify the bug is fixed and mark the task done

AGENTE
  1. 1

    Identify the command that proves the fix: the test that originally failed

  2. 2

    Run that test now, not a cached or previous result

  3. 3

    Read the full output and exit code

  4. 4

    Check whether output confirms 0 failures

  5. 5

    Report completion with the command output as evidence, or report the actual failure if the test still fails

SALIDA

Task marked complete with attached test output showing 0 failures, or honest status report with evidence of remaining failure

Instalación

clawhub install kjaylee/verify-before-done

Ejecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.

Enlaces