arbiterforge/ca-context-check
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.
npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-context-check
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.
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.
commit that touches a drift_trigger source. No manual intervention needed
for the common case.
$ca-create-context.$ca-status.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.
Take arbiterforge/ca-context-check from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.