Files
praxis/skills/verification/SKILL.md
T
阿白叔andClaude Opus 4.7 ea1819f1d2 feat: rename to praxis, package as Claude Code plugin
Reframe team-guide as praxis (Greek for "practice"): Simgreek's coding
agent rulebook, distributed as a Claude Code plugin so SessionStart
hook can force-inject the using-praxis bootstrap.

- Add .claude-plugin/{marketplace,plugin}.json: makes this repo a
  one-plugin marketplace installable via /plugin marketplace add.
- Add hooks/{hooks.json,session-start,run-hook.cmd}: SessionStart
  hook reads using-praxis SKILL.md and injects it into context as
  hookSpecificOutput.additionalContext (Claude Code) or
  additional_context (Cursor) or additionalContext (Copilot CLI).
- Migrate library/<topic>/SPEC.md → skills/<topic>/SKILL.md with
  YAML frontmatter (name + when-to-invoke description).
- Add skills/using-praxis: bootstrap with iron law, red-flags table,
  catalog, instruction priority, sub-agent stop, Codex/Cursor fallback.
- Add skills/debugging: 4-phase root-cause investigation with
  3-fixes-failed → architectural problem rule.
- Add skills/verification: evidence-before-claims gate with
  rationalization table.
- Drop library/, references in AGENTS.md updated to skills/.
- Rename throughout: team-guide → praxis.
- README rewritten with both install paths (plugin / external spec)
  and updated bootstrap prompt.

Codex / Cursor / non-Claude users still get the spec by reading
AGENTS.md and skills/ files manually — only the auto-injection
requires Claude Code.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-25 18:02:48 +08:00

4.4 KiB

name, description
name description
verification Use before claiming work is complete, fixed, or passing — requires running verification commands and reading output before making any success claim; evidence before assertions

Verification — evidence before claims

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 turn, you cannot claim it passes.

The gate

Before claiming any status or expressing satisfaction:

  1. Identify the command that proves the claim.
  2. Run it (fresh and complete — not a partial check, not a remembered previous run).
  3. Read the full output. Check the exit code. Count failures.
  4. Verify the output confirms the claim.
    • If yes: state the claim with the evidence.
    • If no: state the actual status with the evidence.
  5. Only then make the claim.

Skipping any step is lying, not verifying.

Common claims and what proves them

Claim What proves it What does NOT prove it
Tests pass Test command output: 0 failures "Should pass", a run from earlier
Linter clean Linter output: 0 errors Partial check, extrapolation
Build succeeds Build command exits 0 Linter passing, logs look good
Bug fixed Test the original symptom — passes Code changed, "assumed fixed"
Regression test works Red → green: test fails before fix, passes after Test passes once after fix
Sub-agent completed VCS diff shows the changes Sub-agent reports "success"
Requirements met Line-by-line checklist "All tests pass"

Red Flags — STOP

If you catch yourself doing any of these, you're about to make an unverified claim. Stop, run the verification, then continue.

  • Using "should", "probably", "seems to", "I think"
  • Saying "Great!", "Perfect!", "Done!" before running anything
  • About to commit / push / open a PR without re-running checks in this turn
  • Trusting a sub-agent's success report without diff inspection
  • Relying on partial verification (one file checked, claim covers many)
  • "Just this once"
  • Tired and wanting the work over
  • Any wording implying success without evidence in this turn

Rationalizations

Excuse Reality
"Should work now" RUN the verification
"I'm confident" Confidence ≠ evidence
"Just this once" No exceptions
"Linter passed" Linter ≠ compiler ≠ tests
"Agent said success" Verify independently
"I'm tired" Exhaustion ≠ excuse
"Partial check is enough" Partial proves nothing about the rest
"Different words, so the rule doesn't apply" Spirit over letter

Patterns

Tests:

✅ Run `npm test` → output: "34 passing" → "All tests pass (34/34)."
❌ "Should pass now." / "Looks correct."

Regression test (red-green):

✅ Write test → run (pass) → revert fix → run (FAIL) → restore fix → run (pass)
❌ "I've added a regression test." (without red-green proof)

Build:

✅ Run `npm run build` → exit 0 → "Build passes."
❌ "Linter passed, build should be fine." (linter doesn't compile)

Requirements:

✅ Re-read the spec → check each line → report gaps or completion
❌ "Tests pass, so we're done." (tests ≠ requirements)

Sub-agent delegation:

✅ Sub-agent reports success → run `git diff` → confirm the changes
   exist and are correct → report actual state
❌ Trust the sub-agent report

When to apply

Always before:

  • Any variation of "done", "complete", "fixed", "passing"
  • Any expression of satisfaction about work state
  • Committing, opening a PR, declaring task complete
  • Moving to the next task in a multi-step plan
  • Delegating verification to a sub-agent (verify their result yourself)

The rule applies to exact phrases, paraphrases, synonyms, and any implication of success. "Spirit over letter."

Why this matters

Unverified claims:

  • Break the user's trust ("I don't believe you")
  • Ship undefined functions or missing requirements
  • Waste time on false completion → redirect → rework

Honesty is a core value. The cost of running the verification command is small. The cost of being wrong is large.

Bottom line

Run the command. Read the output. Then claim the result. Every time.