factcheck-guard

Solid

Use this skill when making any factual claim about the codebase — existence, absence, or behavior. Converts the claim-verification rule into a systematic action protocol that prevents false assertions from grep-only results.

AI & Automation 552 stars 45 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
91
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# FactCheck Guard — Runtime Claim Verification Prevents false claims about the codebase. Grep results are hypotheses, not proof. Every assertion about "what the code does" must be verified by reading the actual code. ## Why This Exists An 80% false claim rate was observed when agents trusted grep results without reading files. The pattern repeats: grep finds a string, agent asserts behavior, behavior is wrong. This skill converts the claim-verification guidelines into an actionable protocol. ## Confidence Markers (MANDATORY) Every factual claim about the codebase MUST carry one of these markers: | Marker | Meaning | Requirements | |--------|---------|-------------| | [VERIFIED] | Read the file, traced the logic | Must cite file:line | | [INFERRED] | Based on grep or file name | Must verify before asserting to others | | [UNCERTAIN] | Not yet checked | Must investigate before making the claim | Never promote an [INFERRED] claim to a statement of fact. Never let [UNCERTAIN] appear in a response to the user — investigate first. --- ## Verification Protocol ### Level 1: Existence Claims When asserting "X exists in the codebase": **Step 1 — Search (produces [INFERRED])** ``` Grep/Glob for the pattern. Result: "X appears at path/to/file.ts:42" [INFERRED] ``` **Step 2 — Read the file (required to reach [VERIFIED])** ``` Read path/to/file.ts, locate line 42. Confirm the match is actual code, not a comment or string literal. ``` **Step 3 — Check context** ``` Is the code...

Details

Author
vibeeval
Repository
vibeeval/vibecosystem
Created
8 months ago
Last Updated
6 days ago
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

verify-before-claim

Gate against asserting unverified facts. USE WHEN about to claim that something "doesn't exist" / "is blocked" / "isn't deployed", state a measured value/number, describe how an API behaves, or assert a vendored component's capability — especially from memory or several turns ago. Triggers: "doesn't exist", "is blocked", "already done", "the metric equals", any claim about API/enum/payload, "verify", ��не существует», «заблокировано», «уже сделано», «перепроверь».

0 Updated 3 months ago
akuroglo
AI & Automation Listed

verify

Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.

55 Updated 4 days ago
yha9806
AI & Automation Listed

fact-check

Enforces evidence-based reasoning for any task that involves making factual claims about a codebase — debugging, bug fixing, code investigation, code modification, AND explaining what code does, answering "where is X" / "what does Y do" / "is this safe", or summarizing behavior. Use this skill whenever the user asks to fix a bug, investigate an issue, modify existing code, trace a problem, debug behavior, refactor, change, update code, or explain/locate/audit any part of the codebase. This skill ensures Claude gathers real evidence from source code, docs, git history, and runtime behavior before making any claim — never guessing, never paraphrasing comments as fact, never relying on training memory. Even if the task seems straightforward, use this skill to guarantee that every claim and recommendation is grounded in verified facts.

0 Updated 2 months ago
Stoica-Mihai