completion-proof
Verify a software task before claiming it is complete. Use after implementation or repair to connect the requested outcome to executed checks, observed results, changed files, and remaining risks.
trugurpala · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add trugurpala/divan --skill completion-proof技能说明
name: completion-proof description: Verify a software task before claiming it is complete. Use after implementation or repair to connect the requested outcome to executed checks, observed results, changed files, and remaining risks.
Completion Proof
Before saying done:
- restate the requested outcome;
- inspect the final diff;
- run the narrowest behavior check that proves the change;
- run applicable repository gates such as tests, typecheck, lint, build, migration validation, or security checks;
- separate pre-existing failures from introduced failures;
- report skipped or unavailable checks explicitly;
- identify remaining material risk.
When the project maintains a status/operations document or the user requested durable continuity, update that existing record with the outcome, current check evidence, remaining limits, and next open step. Do not create a duplicate document for a trivial edit or treat saved evidence as a substitute for a fresh check.
Use observed language: passed, failed, blocked, or not run.
Never convert a timeout, missing tool, skipped test, or unobserved deployment into success.
Do not claim production publication unless the published artifact or live result was actually verified.