attune-ai: Skill for Claude Code

Verify

IMPORTANT: Start your response by telling the user:

Verify — Fact-checking the named entities in this content against the project as source-of-truth.

What It Does

/verify is the output-side fact-checker for LLM-generated content (docs, READMEs, tutorials). It catches the hallucination classes that unit tests never see — an invented CLI flag, an import of a package that doesn't exist, a dead cross-reference, a wrong count — by confirming the named entities in the content actually exist.

It runs in two layers:

1. Deterministic checkers (attune_verify, authoritative): the top-level package of each import resolves via find_spec, CLI flags appear in --help, markdown links resolve under the project root, numeric claims match a declared count source. These are ground truth — no LLM, no guessing.
2. Ambient semantic cross-check (you, the agent): after the deterministic pass, read the content against its source and flag claims the checkers can't see (a security caveat dropped, a route path that's plausible-but-wrong, a private submodule of an installed package that doesn't actually exist — the import checker only validates the top-level package, so from pkg.fake_sub import X passes deterministically when pkg is installed). This layer is a cross-check only — it over-flags on truncated context, so never let it override a deterministic pass. If the deterministic layer says a top-level import resolves, it resolves.

How To Run It

Shared command workspace (preferred)

Open adapter verify with the validated generated-content path and optional hard_gate=true for pipeline callers. The invocation authorizes this read-only run, so there is no confirmation action. Execute attune_verify.verify exactly as below and publish its authoritative outcome as deterministic_result, retaining every finding's kind, severity, detail, evidence, and location.

Perform the ambient semantic pass only after the deterministic result and publish it as cross_check_result. Ambient findings remain explicitly labeled warnings and cannot override deterministic entity-existence results. In hard gate mode, any deterministic error keeps hard_gate_passed=false. Checker or cross-check failure must render “did not complete,” never a clean report. Present the terminal widget or Markdown and preserve the full evidence chain in text fallback.