verification-before-done
Skill1 starsChanged 5 months agoMITView on GitHub
Make completion claims only after relevant checks, review, and limitations are explicit. Use before saying done, opening a PR, merging, handing off, or ending a long work session. Also use before final response, handoff, merge, or deployment. Task goal, acceptance criteria, changed files, validation commands, test output, known limitations, and environment constraints. When verifying a change that runs in a browser, app, or service, check the 5 axes of runtime behavior. This pattern is framework-agnostic; apply the axes that match…
3 other projects use a version of this.
Adopted by
Most recently taken up by
- lukashouthoofd/cenekathontheir own version, first seen Nov 8, 2026
- unional/skillstheir own version, first seen Nov 6, 2026
- CarbeneAI/Forgetheir own version, first seen Apr 22, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- CarbeneAI/Forge★ 9same name
- lukashouthoofd/cenekathon★ 1same name
- unional/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- advanced-orchestrationSkill
- architect-agentSkill
- implementer-agentSkill
- quality-councilSkill
- reviewer-agentSkill
- tester-agentSkill
- writer-critic-pairSkill
- authoring-skillsSkill
- api-endpoint-qualitySkill
- async-job-qualitySkill
- auth-qualitySkill
- db-migration-qualitySkill
- frontend-state-qualitySkill
- acceptance-criteriaSkill
- adaptive-flowSkill
- adaptive-prompt-selectionSkill
- adversarial-code-reviewSkill
- architecture-decision-recordsSkill
- brainstormingSkill
- brownfield-spec-enhancementSkill
- bug-fix-lifecycleSkill
- checkpoint-validationSkill
- cicd-integrationSkill
- clarify-before-codeSkill
- claude-code-hooks-packSkill
- code-context-packSkill
- code-intelligence-reviewSkill
- context-policySkill
- context-rich-implementationSkill
- crash-proof-planningSkill
- critique-pass-protocolSkill
- dependency-aware-task-orderingSkill
- deprecation-migrationSkill
- disciplined-diagnosisSkill
- docs-authorSkill
- executing-plansSkill
- external-skillSkill
- finishing-a-development-branchSkill
- git-guardrailsSkill
- goal-driven-executionSkill
- grill-user-before-buildingSkill
- guard-bypass-protocolSkill
- improve-codebase-architectureSkill
- incremental-reviewSkill
- issue-slicingSkill
- lessons-learned-dbSkill
- loop-engineeringSkill
- model-aware-configSkill
- model-weakness-memorySkill
- multi-repo-learningSkill
- orchestration-workflowsSkill
- plan-driven-executionSkill
- plan-from-specSkill
- prd-from-contextSkill
- project-constitutionSkill
- prompt-architectureSkill
- prototype-before-commitmentSkill
- quality-engineSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Use before saying done, opening a PR, merging, handing off, or ending a long work session.
- Distinctive: line 29
When verifying a change that runs in a browser, app, or service, check the 5 axes of runtime behavior.
- Very specific: line 40
Claude Code (browser): use chrome-devtools MCP for DOM/console/network/visual.
- Distinctive: line 46
Run the smallest relevant checks first, then broader validation when feasible.
- Distinctive: line 50
Do not convert environment limitations into success claims.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Verification Before Done
Purpose
Make completion claims only after relevant checks, review, and limitations are explicit.
When to use
Use before saying done, opening a PR, merging, handing off, or ending a long work session. Also use before final response, handoff, merge, or deployment.
Inputs
Task goal, acceptance criteria, changed files, validation commands, test output, known limitations, and environment constraints.
5-axis runtime verification (abstract)
When verifying a change that runs in a browser, app, or service, check the 5 axes of runtime behavior. This pattern is framework-agnostic; apply the axes that match your runtime.
| Axis | What to verify | Evidence |
| DOM / state | The rendered output matches the spec (or pre-change baseline). | Screenshot, DOM diff, snapshot test. |
| Console / logs | No new errors, warnings, or unhandled rejections. | Console capture, log diff. |
| Network / API | The expected requests fire with the expected payloads; responses match the spec. | Network trace, API contract test. |
| Performance | LCP / INP / CLS / TTFB / API p99 are within "Good" thresholds. | CWV report, perf budget gate. |
| Visual | The UI renders correctly across the supported viewports / themes. | Screenshot diff across breakpoints. |
For multi-CLI projects, the 5 axes map to specific tools per CLI:
- Claude Code (browser): use
chrome-devtoolsMCP for DOM/console/network/visual; Lighthouse for performance. - Other CLIs (non-browser): substitute network/API/console equivalents; visual axis becomes "output file diff" or "headless screenshot".
Workflow
- Map acceptance criteria to concrete evidence: tests, validation, inspection, or user confirmation.
- Run the smallest relevant checks first, then broader validation when feasible.
- Record exact commands and outcomes, including failures and warnings.
- Apply the 5-axis runtime verification for any user-facing or latency-sensitive change.
- Inspect the final diff for scope, secrets, attribution, generated files, and stale notes.
- Do not convert environment limitations into success claims.
- End with a clear status: passed, failed, blocked, or partially verified.
Outputs
A verification report with exact commands, outcomes, evidence coverage, 5-axis matrix, limitations, and final readiness status.
Failure modes
- Reporting tests as passed when they were not run.
- Claiming success without running checks.
- Using broad validation to hide a missing targeted check.
- Ignoring failed checks because the patch looks correct.
- Skipping one of the 5 axes on a user-facing change.
- Omitting environment limitations.
- "It works on my machine" — local verification is not p75 user verification.
Verification checklist
- Acceptance criteria have matching evidence.
- Exact commands and outcomes are listed.
- Failures or limitations are visible.
- Final status is not overstated.
- All
npm run validate:*commands invoked in this change exited 0 (record exit codes in commit body). - DOM/state axis captured: screenshot, DOM diff, or snapshot test attached for any UI change.
- Console/logs axis captured:
console.log/error/warnoutput recorded, zero new unhandled rejections. - Network/API axis captured: request/response trace or contract test recorded for any API change.
- Performance axis captured: LCP / INP / CLS / TTFB / API p99 numbers recorded for any latency-sensitive change.
- Visual axis captured: screenshot diff across the supported breakpoints (mobile, tablet, desktop).
- Each check is recorded as
PASS/FAIL/LIMITATION:— no "looks good" or "feels right".
Related skills
This skill is the evidence bar that backs the goal-driven member of the four-part engineering discipline set (think-before-coding, simplicity-first, surgical-changes, goal-driven):
skills/core/goal-driven-execution/SKILL.md— turns an imperative into a verifiable goal whose success condition is checked here.skills/prompts/karpathy-engineering-discipline/SKILL.md— Think Before Coding and Surgical Changes.skills/prompts/anti-overengineering/SKILL.md— Simplicity First.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

