Agent SkillsHashWarlock/nobody-plans-for-pi › nobody-verifies-before-completion

nobody-verifies-before-completion

GitHub

强制在声称工作完成前执行验证命令并检查输出,禁止无证据断言成功。确保测试、构建或修复结果真实可靠,防止未经验证即提交或报告通过。

skills/nobody-verifies-before-completion/SKILL.md HashWarlock/nobody-plans-for-pi

Trigger Scenarios

准备声明任务已完成 确认Bug已修复 报告测试或构建通过

Install

npx skills add HashWarlock/nobody-plans-for-pi --skill nobody-verifies-before-completion -g -y
More Options

Use without installing

npx skills use HashWarlock/nobody-plans-for-pi@nobody-verifies-before-completion

指定 Agent (Claude Code)

npx skills add HashWarlock/nobody-plans-for-pi --skill nobody-verifies-before-completion -a claude-code -g -y

安装 repo 全部 skill

npx skills add HashWarlock/nobody-plans-for-pi --all -g -y

预览 repo 内 skill

npx skills add HashWarlock/nobody-plans-for-pi --list

SKILL.md

Frontmatter
{
    "name": "nobody-verifies-before-completion",
    "description": "Use when about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims"
}

Verification Before Completion

Overview

Claiming work is complete without verification is dishonesty, not efficiency.

Core principle: Evidence before claims, always.

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you haven't run the verification command in this message, you cannot claim it passes.

The Gate

Before claiming ANY status:

  1. IDENTIFY — What command proves this claim?
  2. RUN — Execute the FULL command (fresh, complete)
  3. READ — Full output, check exit code, count failures
  4. VERIFY — Does output confirm the claim?
  5. ONLY THEN — Make the claim

Skip any step = lying, not verifying.

Common Failures

Claim Requires Not Sufficient
Tests pass Test command output: 0 failures Previous run, "should pass"
Build succeeds Build output: exit 0 Linter passing
Bug fixed Original symptom test: passes Code changed, assumed fixed
Requirements met Line-by-line checklist Tests passing

Red Flags — STOP

  • Using "should", "probably", "seems to"
  • Expressing satisfaction before verification ("Great!", "Done!")
  • About to commit/push without verification
  • Trusting subagent success reports without checking
  • Relying on partial verification

Rationalization Prevention

Excuse Reality
"Should work now" RUN the verification
"I'm confident" Confidence ≠ evidence
"Just this once" No exceptions
"Partial check is enough" Partial proves nothing
"Agent said success" Verify independently

The Bottom Line

Run the command. Read the output. THEN claim the result. Non-negotiable.

Version History

  • fc2edc0 Current 2026-07-25 05:06

Same Skill Collection

skills/nobody-brainstorms/SKILL.md
skills/nobody-debugs/SKILL.md
skills/nobody-executes-plans/SKILL.md
skills/nobody-finishes-a-development-branch/SKILL.md
skills/nobody-receives-code-review/SKILL.md
skills/nobody-requests-code-review/SKILL.md
skills/nobody-uses-git-worktrees/SKILL.md
skills/nobody-uses-tdd/SKILL.md
skills/nobody-writes-plans/SKILL.md
skills/nobody-writes-skills/SKILL.md
skills/using-plans-for-nobody/SKILL.md

Metadata

Files
0
Version
fc2edc0
Hash
cdeb0567
Indexed
2026-07-25 05:06

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-21 04:44
浙ICP备14020137号-1 $방문자$