agentleFS
Sign inStart free
haintbotasthaintbotast/coding-agent-instructions/skills/verification-before-completion/SKILL.md

verification-before-completion

Skill0 starsChanged 22 days agoMITView on GitHub

Use when about to claim work is complete, fixed or passing: before committing, opening a PR, or reporting success. Requires fresh verification evidence for every claim. Not for designing tests, that is test-driven-development.

189 other projects use a version of this, 134 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 20 projects that use this

  • jh941213Skill

    docs-ci

    문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.

    Also in 3 projects that use this

  • jh941213Skill

    docs-interfaces

    API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.

    Also in 3 projects that use this

  • +3 more from Leodorareluctant259
  • +4 more from jh941213

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before ANY status claim or expression of satisfaction:

    line 18

“Common” is measured: kept by at least 6 in 10 of the 177 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Verification Before Completion

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

Claiming work is complete without verification is dishonesty, not efficiency. If you haven't run the verification command in this message, you cannot claim it passes.

The Gate Function

Before ANY status claim or expression of satisfaction:

  1. IDENTIFY — what command proves this claim?
  2. RUN — execute the full command, fresh and complete.
  3. READ — full output, exit code, failure count.
  4. VERIFY — does the output confirm the claim? If no: state the actual status with evidence.
  5. ONLY THEN — make the claim, WITH evidence.

Skip any step = lying, not verifying.

What Each Claim Requires

ClaimRequiresNot sufficient
Tests passTest output: 0 failuresPrevious run, "should pass"
Linter cleanLinter output: 0 errorsPartial check
Build succeedsBuild exit 0Linter passing
Bug fixedOriginal symptom re-tested: passesCode changed, assumed fixed
Regression test worksRed-green verified (revert → fail → restore → pass)Test passes once
Agent/subagent completedVCS diff shows the changesAgent's "success" report
Requirements metLine-by-line checklist vs planTests passing

Red Flags — STOP

  • "Should", "probably", "seems to" in a status statement
  • "Great!", "Perfect!", "Done!" before verification
  • About to commit/push/PR without running verification
  • Trusting a subagent's success report without checking the diff
  • Tired and wanting the work to be over — exhaustion is not an excuse

Rule applies to exact phrases, paraphrases, and ANY implication of success.

Distilled from obra/superpowers (MIT © Jesse Vincent / Prime Radiant), v6.1.0 @ f268f7c.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free