From cross-checker
Verify every claim from multiple independent angles -- code, docs, tests, git history. Use when you need high confidence that something is correct before acting on it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cross-checker:cross-checkerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Never trust a single source. Verify from at least two independent angles before accepting a claim as fact.
Never trust a single source. Verify from at least two independent angles before accepting a claim as fact.
For any claim, check it against multiple sources:
Read the actual file. What does the code do? This is the strongest evidence.
What do the tests expect? Tests reveal intended behavior. If a test expects validateToken to return false for expired tokens, that's the designed behavior.
What was the original intent? Git blame and commit messages reveal why code was written. "commit abc123: fix token expiration check to reject tokens older than 24h"
README, comments, JSDoc, API docs. Do they match the code? If docs say one thing and code does another, the code is truth but the discrepancy matters.
Config files, environment variables, feature flags. Runtime behavior may differ from what the code looks like.
Package versions, API compatibility, deprecated features. A function might exist in the code but be broken due to a dependency update.
| Situation | Minimum angles needed |
|---|---|
| Stating a fact to the user | 1 (read the code) |
| Recommending a code change | 2 (code + tests or git history) |
| Security-related claims | 3 (code + tests + docs/config) |
| Production deployment advice | 3 (code + config + git history) |
| "This is safe to delete" | 3 (code + grep for references + tests) |
npx claudepluginhub a-ariff/ariff-claude-plugins --plugin cross-checkerValidates factual claims in code reviews, system analysis, documentation, and test reports using tools; prohibits superlatives and unverified metrics.
Validates claims through tool execution, avoids superlatives and unsubstantiated metrics. Use when reviewing codebases, analyzing systems, or reporting test results.
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.