context-check
Optional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
npx skills add arbiterForge/codeArbiter --skill context-check --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# context-check An optional, on-demand drift audit for bypass cases: a merge or an external edit drifted a tracked source file you are not about to commit, so commit-gate's Phase 5.5 auto-heal did not fire. This skill reports stale docs and lets you act on each one individually. This skill is NOT in the daily loop. Commit-gate auto-heal (Phase 5.5, `heal_worklist`) owns the routine maintenance path. Invoke this only when drift was introduced outside a commit (e.g. a direct push, a merge you did not author, a manual file edit). ## Pre-flight Read these before computing drift: 1. `.codearbiter/.provenance/` — the per-doc provenance records. Load all records via `load_provenance_dir` from `{{PLUGIN_ROOT}}/hooks/_provenancelib.py`. 2. `.codearbiter/code-map.md` — coarse concern map; read to orient on which modules the stale docs govern. ## Flow ### Step 1 — Compute drift Use `_provenancelib` helpers in this order: 1. `load_provenance_dir(root + "/.codearbiter/.provenance/")` — returns the provenance map `{doc: record}`. 2. Collect all `drift_trigger: true` paths across all records. 3. `batch_hash(paths, runner)` — hash every existing path in one git call. 4. `compute_drift(provenance_m
- Pre-flight
- Flow
- Step 1 — Compute drift
- Step 2 — Report stale docs
- Step 3 — Per-doc action loop
- Hard rule
What does the context-check skill do?
Optional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill context-check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.