- Home
- Skills
- Testing & Debugging
- Verification-Before-Done
Works with the AI tools you already use
Verification-Before-Done
It treats verification as a first-class artifact, not an afterthought.
$5
Verification-Before-Done
Example session with this skill installed
I fixed a bug where our Node/Express app sent password reset emails twice. The job was queued in both the controller and a Mongoose post-save hook, and I removed the hook. Is it actually done?
- Read your context and instructions
- Compiled the verification-before-done
Verification plan for the duplicate password reset email fix. It is not done until the checks below produce evidence.
Definition of "working"
- One reset request produces exactly one job in the queue and one email sent
- Other flows that relied on the post-save hook still behave as before
- The reset link in the email still works end to end
Checks (evidence over inference)
| # | Check | Evidence to capture |
|---|---|---|
| 1 | Trigger one reset in staging | Queue shows 1 job for that user ID |
| 2 | Inspect mail provider log | 1 message to the test address |
| 3 | Search the codebase for other callers of the hook's function | List of call sites, or "none" |
| 4 | Save a user through a non-reset path (profile update) | No reset job queued |
| 5 | Click the reset link, set a new password | Login with the new password succeeds |
| 6 | Add a test asserting the enqueue is called once | Test fails on the old code, passes on the new |
"The hook is gone so it must be fixed" is inference. Checks 1, 2 and 6 turn it into evidence.
Evidence trail
Record per check: date, environment, command or action, observed result, link to log or screenshot. Attach it to the PR.
Next steps
- Run checks 1 to 5 in staging and fill in the trail
- Write the regression test from check 6
- Mark done only when every row has evidence
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
'Should work now' is the most expensive sentence in software — it means the change was reasoned about, not observed, and the next person to touch this code will pay for that assumption. This skill builds the verification protocol for your specific change: the exact commands to run, the outputs to observe, the edge cases to test manually, and the signals that confirm the fix didn't introduce a regression. It treats verification as a first-class artifact, not an afterthought. Use it before you close any ticket — give it your change, your environment, and what you've already tested; it returns the complete verification checklist that lets you say 'done' and mean it.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 3 months ago
- Passed all security checks, Safe to install