ClaudeMods
☰
All projectsCommunity submissionsPromptsToolsFree toolsGuidesSponsors1 feed slots leftDashboards & HUD252Usage & costs57Security & privacy58Memory & context23Workflows & CI272Git & code review36Multi-agent orchestration118Prompts & input28Notifications & reminders36Games & entertainment71Themes & appearance61Audio & multimedia12Tools & integrations113Development & debugging28Other101
EN
● 0 online · Views 0 times
SponsorsSubmit a project
GitHub repositories · by LeeHigma0201

check-ledger

Records which real checks ran and which files changed after them; status line, /evidence, and an evidence tool Claude reads before claiming tested.

LeeHigma0201@LeeHigma0201

LeeHigma0201/claude-code-mods/tree/main/mods/check-ledger

Translated

About this mod

A Claude Code mod that tracks the evidence behind CLAUDE.md status claims. It listens to Bash and edit tool calls to detect real checks (tests, type-checker, build, linter, validators, plugin test/validate) versus non-qualifying ones, then reports a compact status line such as ✓ pnpm run typecheck · 2 files unchecked or ✗ pnpm test. The /evidence command shows the last 10 checks, files edited after the last passing check, and the strongest status word the ledger supports (tested vs implemented locally). An mcp__check-ledger__evidence tool exposes the same report to the model, requiring a local listener; if refused, it logs a line while the status line and /evidence keep working. State is in-memory per session, observability-only, and never blocks or mutates calls. Includes 3 tests runnable via claude plugin test ..

Installation

Check the author's README for the marketplace and plugin name first. Commands may change as the repository evolves.

claude plugin marketplace add LeeHigma0201/claude-code-mods
claude plugin install check-ledger
Original text / README

check-ledger

Keeps the evidence behind the CLAUDE.md status words: which real checks ran, whether they passed, and which files changed after the last pass.

  • Real check means the repo's tests, type-checker, build, linter or validator: pnpm test|typecheck|build|lint, vitest, jest, pytest, tsc, cargo/go/swift test/build, eslint, claude plugin test|validate, and similar. Syntax-only checks (bash -n, node --check, json.tool), --help and --version don't count. The outcome comes from the Bash call's own error flag.
  • Status line: ✓ pnpm run typecheck · 2 files unchecked, or ✗ pnpm test.
  • /evidence: the last 10 checks, the files edited after the last passing check, and the strongest word the ledger supports: tested (every edit has a passing check after it) or implemented locally.
  • evidence tool (mcp__check-ledger__evidence): the same report for Claude to read before it says "tested". The tool needs a local listener. Where that is refused (a sandboxed launch) it logs one line, and /evidence and the status line still work.

Limits: the ledger lives in the module and restarts on a reload or a new session. It only sees calls made in this session, including its subagents. It observes; it never blocks or changes a call.

Hooks: session.start, tool.call (Bash and edit tools, passed through unchanged), command.run. Calls: $.command.register, $.tool.register, $.ui.status, $.ui.log, $.clock.now.

Test: claude plugin test . (3 tests).

Similar projects