Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

do-it-verify

Estrellas21

Forks2

Actualizado17 de julio de 2026 a las 01:37

Use before any done, fixed, passing, ready, install, or merge claim, and when closing a branch — fresh evidence on this worktree; hooks vary by host, this skill is the checklist.

Instalación

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.

Ejecutar en Manus

Fuente

tdwhere123

tdwhere123/do-it

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	do-it-verify
description	Use before any done, fixed, passing, ready, install, or merge claim, and when closing a branch — fresh evidence on this worktree; hooks vary by host, this skill is the checklist.

Do-It Verify

Evidence before status. This skill is the universal checklist; host hooks may block, remind, or be unavailable. Never let a hook substitute for claim-specific proof.

Leading words: fresh evidence, this worktree, claim.

Before Any Done Claim

Name the claim (tests pass, bug fixed, review clean, ready to merge, …).
Choose the command or inspection that proves it on this branch/worktree.
Run it fresh (or NOT_VERIFIED with why).
Compare output to the claim.
Report the exact result — not optimism.

Old CI, worker summaries, and memory are context, not closeout proof. Prefer checks that hit the changed surface.

Claim Shortcuts

Claim	Needs
`tests pass`	Fresh test output + exit code
`bug fixed`	Original symptom or regression now green
`review clean`	No unresolved Blocking/Important on both axes
`ready to merge`	Verify + review + intended diff + commit policy
`ready to install`	Package/doctor/setup evidence for the changed surface
`runs in production`	Production-side evidence (health check, metric, log) — local test output alone is not proof

Branch Closeout

When closing a branch, PR, merge, or cleanup:

Verification evidence for the delivery claim
Review / fix status
Intended diff only
Deferred-marker sweep: grep the project's convention (e.g. TODO(@owner)) and surface leftovers in the claim
Rollback note for merge/release/install changes
Explicit path: merge / PR / keep / discard (discard needs confirmation)
Clear .do-it/runtime/pointer when merged or discarded

Subagents do not commit, merge, push, or delete branches by default.

Failure

If verification fails: do not soften wording → capture → debug/fix → re-verify. If blocked: NOT_VERIFIED + missing command — never claim done / ready / fixed for that surface.

Output

Claim; branch/worktree; evidence command; VERIFIED / FAILED / NOT_VERIFIED; remains; residual risk; next action.

Más de este repositorio

mismo repositorio

do-it-code-quality

tdwhere123/do-it

Use when writing or designing code: name premise and blast radius, deepen modules at seams, TDD at agreed seams, diagnose before patching, and keep producer→consumer contracts honest.

2026-07-1721

do-it-decide

tdwhere123/do-it

Use when premises or options must be pressure-tested, a short plan/handoff is needed, or a large plan must be sliced — grill facts locally, ask decisions one at a time.

2026-07-1721

do-it-handbook

tdwhere123/do-it

Use when a project needs a lean `.do-it/handbook/` for stable project truth plus `.do-it/worklog/` for daily or goal notes.

2026-07-1721

do-it-retrospective

tdwhere123/do-it

Use only when the user explicitly asks to enable, disable, inspect, report, or persist opt-in local do-it behavioral feedback.

2026-07-1621

do-it-router

tdwhere123/do-it

Use when starting any non-trivial repo task: pick Light / Standard / Heavy tier, then self-select meaning skills — not a fixed pipeline.

2026-07-1621

do-it-context

tdwhere123/do-it

Use when repo terms or invariants are drifting, or when user/docs/code naming disagrees and a canonical glossary is needed — `.do-it/CONTEXT.md` is the downstream source of truth for names, relationships, and facts.

2026-07-1221

Do-It Verify

Evidence before status. This skill is the universal checklist; host hooks may block, remind, or be unavailable. Never let a hook substitute for claim-specific proof.

Leading words: fresh evidence, this worktree, claim.

Before Any Done Claim

Name the claim (tests pass, bug fixed, review clean, ready to merge, …).

Choose the command or inspection that proves it on this branch/worktree.

Run it fresh (or NOT_VERIFIED with why).

Compare output to the claim.

Report the exact result — not optimism.

Old CI, worker summaries, and memory are context, not closeout proof. Prefer checks that hit the changed surface.

Claim Shortcuts

Claim

Needs

tests pass

Fresh test output + exit code

bug fixed

Original symptom or regression now green

review clean

No unresolved Blocking/Important on both axes

ready to merge

Verify + review + intended diff + commit policy

ready to install

Package/doctor/setup evidence for the changed surface

runs in production

Production-side evidence (health check, metric, log) — local test output alone is not proof

Branch Closeout

When closing a branch, PR, merge, or cleanup:

Verification evidence for the delivery claim

Review / fix status

Intended diff only

Deferred-marker sweep: grep the project's convention (e.g. TODO(@owner)) and surface leftovers in the claim

Rollback note for merge/release/install changes

Explicit path: merge / PR / keep / discard (discard needs confirmation)

Clear .do-it/runtime/pointer when merged or discarded

Subagents do not commit, merge, push, or delete branches by default.

Failure

If verification fails: do not soften wording → capture → debug/fix → re-verify. If blocked: NOT_VERIFIED + missing command — never claim done / ready / fixed for that surface.

Output

Claim; branch/worktree; evidence command; VERIFIED / FAILED / NOT_VERIFIED; remains; residual risk; next action.