I could have created a generic "bug fix" skill. A template that asks for the symptom, expected behavior, what's already been tried. Useful. Generic. Forgettable.
Instead, I looked at my git log. On this project, 8 out of 30 commits touch the same Node.js subsystem. Always the same patterns: API timeout, slug regex, corrupted JSON file. The skill I created doesn't ask for the symptom — it directly reads the 3 files that explain 80% of failures, in order. That's the difference between a generic template and a custom skill.
The git log is the most honest documentation of what you actually do. Here's how to use it to generate skills that auto-trigger.
The audit: what your git log really reveals
Start with this command:
