Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

context-check (Doc Drift Audit)

An on-demand audit that finds provenance-tracked docs gone stale from out-of-commit source changes and lets you re-scout, re-baseline, or defer each one.

Dev & CodingAdvanced★ 147⑂ 9AI score 7/10Last updated: Oct 11, 2026

What it does

  • Loads every provenance record from .codearbiter/.provenance/, batch-hashes the tracked source paths, and computes which docs are stale.
  • Prints a compact report of stale docs plus the changed or missing paths behind each.
  • Offers three per-doc actions: re-scout (re-read the changed paths and verify claims), re-baseline (silently update hashes for cosmetic changes), defer (leave it for the next session).
  • Enforces a hard rule: never stages or commits — provenance updates ride your next normal commit.

Who it's for

  • Teams already running the codeArbiter plugin with provenance-based doc/code sync.
  • Developers who hit drift from merges, direct pushes, or manual edits that bypass the commit gate.
  • Maintainers who want periodic confidence that documented claims still hold.

Examples

  1. After merging someone else's branch, ask for a context-check → three stale docs surface; re-scout only the refactored module's doc.
  2. A repo-wide formatter run changed whitespace only → choose re-baseline everywhere to refresh hashes without a costly re-scout.
  3. A work-in-progress file shows drift → defer it so commit-gate auto-heal handles it at the next commit.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/arbiterForge/codeArbiter/HEAD/core/surface/skills/context-check/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the core/surface/skills/context-check folder from the GitHub repo arbiterForge/codeArbiter into my ~/.claude/skills/context-check/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/arbiterForge/codeArbiter.git && mkdir -p ~/.claude/skills/context-check && cp -r codeArbiter/core/surface/skills/context-check/* ~/.claude/skills/context-check/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal in your workspace folder.
  2. Clone the repo: git clone https://github.com/arbiterForge/codeArbiter.git
  3. Create the skill folder: mkdir -p ~/.claude/skills/context-check
  4. Copy the files: cp -r codeArbiter/core/surface/skills/context-check/* ~/.claude/skills/context-check/
  5. Important: this skill depends on codeArbiter's hooks/_provenancelib.py and a project-level .codearbiter/.provenance/ directory. Copying the skill alone is not enough — install and initialize the full codeArbiter plugin.
  6. Restart Claude Code, then ask: "run context-check and list stale docs".
View source on GitHub ↗License: AGPL-3.0