trace-scan

# Trace Scan (trace-scan) <!-- routing-eval reads this line; it lives in the BODY so the always-on skill LISTING stays inside Claude Code's budget (1% of the context window) — an overflowing listing gets descriptions truncated or dropped, which strips the very keywords a match depends on. --> Trigger phrases: "scan traces", "trace scan", "AI trace", "check vendor name", "pre-commit audit" Purpose: to bind §4.1/§4.2 to a *gate* rather than to *memory*. If the rule lives only in text, a trace leaks sooner or later; this skill + the hooks stop the leak at commit time. ## When - Before every commit (automatic: `pre-commit` + `commit-msg` hooks). - Before commit-agent-csk proposes a message (manual verification). ## How Pattern list: `./.claude/hooks/trace-blocklist.txt` (grep -iE, one pattern per line). - **Defaults are high-hit:** co-author trailers, auto-generation footers, robot emoji, and AI-assistant/tool brand names. Standalone words that occur too often (model/assistant) are DELIBERATELY excluded. See trace-blocklist.txt for the exact list. - **Vendor name is project-specific:** ADD the name of the third-party template in use to the list (§4.2). Manual scan (a quick look without the hook): ```bash git diff --cached --unified=0 | grep -E '^\+' | grep -Ev '^\+\+\+' \ | grep -iEf .claude/hooks/trace-blocklist.txt ``` ## Hook setup `start.sh` sets `git config core.hooksPath .claude/hooks` (if there is a git repo). The hooks live under `.claude` → they are i...