本文へ移動
cccskills
無料GitHub で公開

verification-before-completion

Never claim completion without fresh verification evidence

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Verification Before Completion

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

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

The Gate

Before claiming ANY success:

1. IDENTIFY → What command proves this claim?
2. RUN → Execute the FULL command
3. READ → Full output, check exit code
4. VERIFY → Does output confirm the claim?
5. CLAIM → Only now, with evidence

Skip ANY step = lying, not verifying.

What Requires Verification

ClaimRequiresNOT Sufficient
"Tests pass"Test output: 0 failures"Should pass", previous run
"Build works"Build output: exit 0Linter passing
"Bug fixed"Test of original symptom"Code changed"
"Linter clean"Linter output: 0 errors"Looks right"
"Feature complete"All requirements checked"Tests pass"

Red Flags - STOP

If you catch yourself:

  • Using "should", "probably", "seems to"
  • Saying "Great!", "Perfect!", "Done!" before running verification
  • About to commit without fresh test run
  • Thinking "just this once"
  • Feeling tired and wanting to be done

STOP. Run the verification.

Rationalization Prevention

You ThinkReality
"Should work now"RUN IT
"I'm confident"Confidence ≠ evidence
"Just this once"No exceptions
"Linter passed"Linter ≠ tests
"I'm tired"Exhaustion ≠ excuse

Correct Patterns

Tests:

✅ [run test] → See "34/34 pass" → "All tests pass"
❌ "Tests should pass now"

Build:

✅ [run build] → See "exit 0" → "Build passes"
❌ "Build looks good"

Requirements:

✅ Re-read requirements → Check each → Report gaps
❌ "Tests pass so it's complete"

Why This Matters

From actual failures:

  • User said "I don't believe you" - trust broken
  • Undefined functions shipped - would crash at runtime
  • Missing requirements - incomplete features
  • Time wasted on false completion → redirect → rework

Bottom Line

Run the command. Read the output. THEN claim the result.

This is non-negotiable.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Complete methodology for preventing AI hallucinations. Use when accuracy is critical and you need Claude to verify before claiming, cite before asserting, and admit uncertainty instead of guessing.

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Transform rough ideas into solid designs through structured questioning

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Canvas API Connection Skill

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Forces every code-related claim to include file:line citations. No citation means the claim must be verified or removed. Use when building documentation, writing code reviews, or any output that others will rely on.

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Assign confidence scores (0-100) to every claim in a response. Helps users understand which parts are verified facts and which are educated guesses. Use when the user needs to know how much to trust each part of the answer.

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Forces Claude to extract exact quotes from files before making claims about them. Prevents hallucinations by grounding every statement in actual text from the codebase. Use when working with large files or unfamiliar code.

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

a-ariff のスキルをすべて見る

このスキルの問題を報告する