Communitygithub.com

brain-marchine/verify-done-skills

Agent skills that refuse Fake Done

verify-done-skills란 무엇인가요?

verify-done-skills is a Claude Code agent skill that agent skills that refuse Fake Done.

지원 대상Claude Code~Codex CLICursor
npx skills add brain-marchine/verify-done-skills

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

verify-done

Agent said Done. Reality must agree.

You MUST run verification before saying the work is finished. Verbal "Done / Fixed / 做完了" without a PASS from the scripts below is Fake Done — forbidden.

When this skill applies

  • User or you claim: Done, Fixed, complete, finished, verified, LGTM, ready to merge
  • Chinese: 做完了、修好了、弄好了、验收通过、可以提交
  • Any UI / layout / overflow / bugfix claim

Hard rules

  1. Do not say Done / Fixed / 做完了 until the check script exits 0 (PASS).
  2. On FAIL (exit 1): show evidence, keep fixing, re-run the script.
  3. Prefer running the bundled script over inventing your own checklist.
  4. If the script path is unclear, locate SKILL.md for this skill and run scripts/check.mjs next to it.

Procedure

1. Locate this skill

Common install paths:

  • Project Cursor: .cursor/skills/verify-done/
  • Project Claude: .claude/skills/verify-done/
  • User Cursor: ~/.cursor/skills/verify-done/
  • User Claude: ~/.claude/skills/verify-done/

2. Run the check (from the user's project root)

node "<path-to-verify-done>/scripts/check.mjs" --cwd . --claim "<exact claim text>"

Windows PowerShell example:

node "$PWD\.cursor\skills\verify-done\scripts\check.mjs" --cwd . --claim "Fixed the inventory overflow"

Optional demo URL check (when a local page should prove a UI fix):

node "<path-to-verify-done>/scripts/check.mjs" --cwd . --claim "Fixed overflow" --url http://127.0.0.1:4173

3. Report in chat (required template)

## verify-done: FAIL | PASS
- Claim: ...
- Checks: git_diff | fake_tests | npm_test | url_probe (list which ran)
- Evidence: (paste key lines from script stdout)
- Next: (if FAIL, concrete fix steps; if PASS, you may say Done)

4. Only after PASS

You may say the work is done. Summarize what passed.

What the script checks

CheckBehavior
git_diffClaimed a fix but no file changes → FAIL
fake_testsVacuous tests (expect(true).toBe(true), empty bodies, it.todo) → FAIL
npm_testIf package.json has test script, runs it (skip if missing)
url_probeIf --url given, FAIL when page still contains overflow-bug / LAYOUT BROKEN

Details: references/fake-done.md

Anti-patterns (do not do)

  • "Tests are green in my head" without running the script
  • Editing the script to force PASS
  • Saying Done because the user sounded impatient
  • Skipping verify on "tiny" UI claims — those are Fake Done hotspots

관련 스킬