메뉴
Use before claiming any implementation is done, fixed, complete, or passing — and before committing or handing work over for testing. Green typecheck/lint is not verification; the changed behavior must be exercised and the evidence shown.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/Harduex/skills --skill verify-before-done명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
The universal base layer of standards for everything a project authors, code and prose alike, derived from the ASD-STE100 controlled-language specification: a controlled naming vocabulary with a per-project glossary, small imperative units with guard conditions first, severity-accurate errors that state consequences, and a document band covering procedural and descriptive writing, sentence-length counting, punctuation, and cohesion. A project's own coding-standards skill and glossary complement and override it. Use when writing or naming code, authoring comments, docstrings, error messages, logs, or commit messages, writing or rewriting a README, specification, runbook, release note, or any technical document, auditing code or a document against a standard, rewriting someone else's prose into the standard, setting up or extending a project glossary, or when the user mentions coding standards, naming conventions, writing style, documentation style, or controlled vocabulary.
Converts an internal artifact — a design spec, a shipped branch or feature, an API or data contract — into a self-contained handoff document an external team can read fast and act on without any internal context. Use when handing a contract, integration guide, or feature description to another team or company, when asked for a handoff document, a client-facing explainer, or a doc to publish outside the repo (Google Doc, wiki, PDF), when converting a spec into something reviewable by people without codebase access, or when folding a published copy's review edits back into the repo source.
Distributes uncommitted working-tree changes back to their originating commits on a multi-commit branch using git commit --fixup and a non-interactive autosquash rebase. Use when the user wants to "distribute" fixes into existing commits, clean up a branch after review feedback, fold review fixups into the right commits, or mentions fixup/autosquash workflows.
| name | verify-before-done |
| description | Use before claiming any implementation is done, fixed, complete, or passing — and before committing or handing work over for testing. Green typecheck/lint is not verification; the changed behavior must be exercised and the evidence shown. |
A change is "done" only when you have watched it work. Static gates (typecheck, lint, even a green unrelated test run) prove the code compiles — not that the feature behaves.
Before saying done / fixed / implemented / passing, or committing a nontrivial change:
Default to chat prose with stable IDs (TC-3, F2) so the human can answer "about F2…".
That is the form they actually engage with.
Say so explicitly: "implemented, NOT verified — needs X" beats a false "done". Never let a handoff imply verification that didn't happen; the human testing your unverified work is the failure mode this skill exists to prevent.
"X broke because Y" and "this fix resolves it" need the same bar: reproduce the failure, apply the change, observe the failure gone. Correlation with your last edit is not causation — environment flakiness confounds it.