learn-from-fixeslisted

# Learn From Fixes A project's git history is a labelled dataset of what its first pass gets wrong. A `fix` commit landing on a file a `feat` commit touched days earlier is not maintenance — it is the feature having shipped broken, with the diagnosis written in the commit message. This turns that history into a ranked list of what to gate. ## 1. Measure ```bash node "${CLAUDE_PLUGIN_ROOT}/scripts/mine-fixes.js" . ``` Add `--json` for machine-readable output, `--window-days=7` for slower-moving repos. It is read-only and never writes to the repo. If it reports no conventional `fix:` commits, say so and stop — the analysis needs conventional subjects, and inventing a ranking without them would be exactly the unverified guess this skill exists to prevent. ## 2. Read the top classes against the real commits The tool ranks by subject-line keywords, which is a proxy — and **measured against a read of the commit bodies, a weak one.** On three production repos the two passes disagreed on magnitude by roughly 8x (ordering/async: 41% / 32% / 40% by reading, 5% / 6% / 3% by regex) and on *which class ranked first*. A body saying "the phone home raced boot and lost" ships under the subject `fix(now): first-paint`; the regex only ever sees the subject. So: the fix:feature ratio, the rework window and the hot-file list are counts and can be quoted. **The class ranking is a starting point, and its number is a floor, not a share.** Before drawing conclusions, read the actual commits