agentsclimarketplace

Verify before done

Skill buildmoonshot/skillpacks/skills/engineering/beginner/verify-before-done

A beginner-to-expert curriculum of drop-in skills for Claude Code, Codex, and any coding agent. Copy-paste ready, tested, not a link farm.

Install
npx -y skills add buildmoonshot/skillpacks --skill verify-before-done

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use after making a code change and before telling the user it is finished or working. Forces the agent to actually check the change — run the test, build, or a concrete trace of the logic — and report real results, instead of optimistically claiming success it hasn't confirmed.

SKILL.md

1.7 KB, as published. Nobody here has run it

Verify Before Done

Do not say a change is "done," "fixed," or "working" until you have evidence that it is.

What counts as evidence

In rough order of strength:

  1. Run it. Execute the test, build, script, or command that exercises the change and read the actual output.
  2. Add a check. If nothing tests this path, write a small test or assertion that would fail before your fix and pass after — then run it.
  3. Trace it. If you genuinely can't run anything, walk the changed logic step by step with a concrete example input and show the result. Say explicitly that this is a trace, not an execution.

How to report

  • If it passed: say so, and briefly say what you ran ("ran npm test — 14 passing").
  • If it failed: say that plainly and show the output. A failure you report is a problem solved; a failure you hide is a problem shipped.
  • If you couldn't verify: say "I couldn't verify this because ___" instead of implying it works. Never let an unverified change wear the word "done."

The rule

"Should work" is not "works." If you didn't check, don't claim it.

Why this matters

The most expensive bug is the one the agent confidently called "fixed." Verification converts confident guesses into either a real result or an honest "not yet" — both of which save the user from discovering the failure in production.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.