From context-grounding
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/context-grounding:context-groundingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read first. Quote second. Claim third. Never skip a step.
Read first. Quote second. Claim third. Never skip a step.
Before making any claim about code, follow this sequence:
Read the actual file. Don't work from memory.
Pull the exact text that supports your claim. Include line numbers.
Now state what you believe, citing the quote as evidence.
Wrong approach: "The auth middleware checks for JWT tokens and returns 401 if invalid." (No evidence. Could be hallucinated.)
Grounded approach: "Reading src/middleware/auth.ts:15-25, the middleware does:
const token = req.headers.authorization?.split(' ')[1];
if (!token) return res.status(401).json({ error: 'No token provided' });
So it extracts the Bearer token from the Authorization header and returns 401 if missing."
Always ground when:
For files over 100 lines:
For files over 500 lines:
Before sending a response, test each factual statement: "Could someone verify this by reading the file I'm referencing?"
If yes: the statement is grounded. If no: you need to add the file reference and relevant quote. If you don't have a file to reference: either find one or mark as unverified.
npx claudepluginhub a-ariff/ariff-claude-plugins --plugin context-groundingProduces grounded, citation-backed responses from source documents via direct quotes, uncertainty permission, and claim verification. Use for analyzing codebases, specs, or long documents.
Verifies factual accuracy of documents against codebase and git history: extracts claims, checks sources, corrects inaccuracies in place, adds summary. Targets reports/plans; auto-detects recent HTML or takes path.
Validates factual claims in code reviews, system analysis, documentation, and test reports using tools; prohibits superlatives and unverified metrics.