Affirm

/affirm — affirm project instruction files

CLAUDE.md, anything under .claude/rules/, and any files they pull in via Claude Code's @import syntax are loaded as Claude's system instructions for this project. A malicious or accidental change can silently re-program Claude. /affirm is the explicit trust gate: bare /affirm shows you what's there; /affirm -a records SHA-256 hashes once you've reviewed; /affirm -r revokes; /affirm --since <iso> reports only what moved after a timestamp. The SessionStart hook compares stored hashes on every session start and warns on any mismatch.

Procedure

Forward args to the CLI verbatim and relay output to the user. No confirmation prompts — the user types -a when they're ready to attest.

The CLI lives at <skill-base-dir>/../../lib/cli.ts.

Bare /affirm — show details

bun run "<skill-base-dir>/../../lib/cli.ts"

Relay the output. This is read-only — nothing is recorded.

/affirm -a (or --apply) — record hashes

bun run "<skill-base-dir>/../../lib/cli.ts" -a

Relay the output. The user invoking -a is the attestation; do not add a separate confirmation step.

/affirm -r (or --revoke) — drop affirmation

bun run "<skill-base-dir>/../../lib/cli.ts" -r

Relay the output.

/affirm --since <iso> — what changed inside a window

bun run "<skill-base-dir>/../../lib/cli.ts" --since <iso>

Relay the output. Read-only. Lists only the tracked files whose mtime falls after <iso>, with their affirmation status and the subjects of any commits that touched them in that window; a file that is touched but still hash-matched is listed without a call to action. continuity's /wrap calls this with the session's session_start so a change the user made themselves gets summarized at the end of the session that made it, rather than surfacing as a trust warning at the start of the next one.

/affirm --help

bun run "<skill-base-dir>/../../lib/cli.ts" --help

Relay the output.

What this skill does NOT do

• Read the contents of CLAUDE.md or rules files. That's the user's job — they're the one attesting.
• Modify any instruction file. Affirmation is hash-only.
• Affirm files the project doesn't reference. Scope is <cwd>/CLAUDE.md + <cwd>/.claude/rules/* plus whatever they @import (followed two levels deep; an import pointing outside the project is hashed but flagged out-of-tree). User-global ~/.claude/CLAUDE.md is out of scope unless a tracked file imports it.
• Prompt the user "are you sure?". The flag is the attestation.

Edge cases

• No instruction files in cwd: the CLI prints a single line and exits. Relay that and stop.
• Unknown flag: the CLI exits 2 with usage. Relay it.
• -a and -r together: the CLI exits 2 with a "mutually exclusive" error. Relay it.
• Hash file at ~/.claude/affirm-hashes.json is missing or unparseable: the CLI treats it as empty and writes a fresh one on next -a. No action needed.