Agent skill · Security

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.

arbiterForgegithub.com/arbiterForgeGitHub ↗
codexclaude-codeAGPL-3.0
Install
npx skills add arbiterForge/codeArbiter --skill ca-context-check --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 1 KB
Bundled scripts: none
Path: plugins/ca-codex/skills/ca-context-check/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 138 · +1 this week
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# $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_trigger` source. 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.

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Hard gate
More from codeArbiter
All skills →
About this skill
What does the ca-context-check skill do?

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.

How do I install it?

Run `npx skills add arbiterForge/codeArbiter --skill ca-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.

Keep going