Skip to content
Back to skills

Verify Before Done

ASecurity

Require fresh evidence before claiming an implementation, fix, build, or test is complete.

  • 14 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 1, 2026
ai-agents

Security analysis

A100/100

Scanned September 1, 2026

npx -y skills add amplifthq/oh-my-dsh --skill verify-before-done --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Verify Before Done?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Verify Before Done
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/amplifthq-verify-before-done/badge)](https://www.skillsdirectory.com/skills/amplifthq-verify-before-done)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: verify-before-done
description: Require fresh evidence before claiming an implementation, fix, build, or test is complete.
whenToUse: Use before any completion claim or handoff.
---

# Verify before done

1. Identify the exact command or observation that proves each claim.
2. Run it fresh after the final edit.
3. Read the complete exit status and relevant output; do not infer one check from another.
4. For a bug fix, reproduce the original symptom or run a regression test that exercises it.
5. Reconcile the implementation against every requested requirement, not only the passing tests.
6. Report the evidence and any check that could not be run. Never replace missing evidence with confidence language.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…