Living Documentation Score (12.3) with CARI. Use when: computing composite documentation health, checking iw verify --score, interpreting the 4-dimension score, investigating low dimension scores, using cari_living_score MCP tool, tracking documentation quality over time.
Architecture diagram validation with CARI. Use when: validating that code matches architecture diagrams, checking component grounding in the index, investigating missing flows, using cari_arch_diff/cari_resolve/cari_component_evidence MCP tools, running iw index arch-check or scan-diagrams.
Use this skill when working in a repository that has an IntentWeave index (`.iw/index.db` or `.iw/rules.yaml` present) — before implementing a feature that touches code you haven't read yourself, before finishing a change or opening a PR, when asked why code works a certain way or what depends on something, or after editing documentation or renaming/moving a symbol. Grounds your understanding of the codebase in its own docs, imports, and git history instead of guessing, and checks changes against the repo's own documented architecture rules before a human reviewer has to. Local SQLite index, $0 cost, no LLM or servers required for the core commands.
Documentation and architecture drift detection with CARI and KG. Use when: checking if docs are stale, finding which docs reference changed code, running doc-health, using cari_check MCP tool, detecting annotation drift, cross-group inconsistency, orphaned sections, or temporal staleness.
Run IntentWeave CARI checks locally and set up GitHub Actions CI. Use when: running iw index commands, checking documentation drift, setting up CI drift detection, diagnosing iw failures, adding drift checks to a pipeline, running code quality analysis with CARI.