Ca context check
Skill arbiterForge/codeArbiter/plugins/ca-codex/skills/ca-context-check
When you can't trust yourself with your code base, trust Arbiter.
npx -y skills add arbiterForge/codeArbiter --skill ca-context-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Optional manual drift audit — report stale provenance-tracked docs, then per stale doc offer re-scout, re-baseline, or defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
SKILL.md
1.3 KB, as published. Nobody here has run it
$ca-context-check — manual drift audit
An optional, on-demand audit for bypass cases: a merge or external edit
changed a tracked source file you are not about to commit, so commit-gate's
auto-heal did not fire. Routes to the context-check skill.
When to use
Use this only when you believe drift was introduced outside a commit (e.g. a
direct push, a merge you did not author, a manual file edit while outside a
normal commit workflow). The SessionStart drift line (backed by
startup_drift_line) is the usual signal that this check is warranted.
When NOT to use
- Routine maintenance — commit-gate auto-heal runs automatically on every
commit that touches a
drift_triggersource. No manual intervention needed for the common case. - Full brownfield re-scan from scratch →
$ca-create-context. - Project state snapshot →
$ca-status.
Hard gate
Read-only unless the user explicitly chooses re-scout (partial scout run) or
re-baseline (hash update in .codearbiter/.provenance/). MUST NOT commit on
its own. MUST NOT modify any derived doc without an explicit user selection.