mine-history

# Commit History Miner ## Overview Verify that the instruction system (AGENTS.md, AGENTS.project.md, `agents/project/domain-context.md`, playbooks) recorded the lessons the repo actually paid for. The day-to-day self-improvement protocol captures lessons one PR at a time; this skill is the periodic sweep that catches what slipped through. **Core principle: every candidate carries commit-hash evidence. A lesson without a commit behind it is speculation, and speculation does not enter the instruction files.** ## When to Use - "mine the history for lessons", "audit the agent files against history" - After a busy stretch of fixes, or roughly monthly (see Cadence) - After adopting this instruction system in a repo with existing history ## Procedure 1. **Read what exists first.** AGENTS.md, AGENTS.project.md, every file in `agents/project/`. Only NEW lessons get reported; re-reporting a covered fact is noise that erodes trust in the sweep. 2. **Scope the window.** First run: full history. Later runs: since the last mining commit (find it with `git log --grep="history-mined" --oneline`). 3. **Probe, in order of yield:** - Reverts: `git log --grep=revert -i --oneline`. Each revert is a paid experiment; the lesson is what not to retry and what worked instead. - Fix chains: group `fix(<scope>):` commits by scope; any scope with a disproportionate count is one misunderstanding surfacing repeatedly. Ask what stable fact would have prevented the cla...