Repo History Book

Use this skill when the user wants more than a changelog:

• "walk me through how this repo evolved"
• "what did the engineers learn building this?"
• "turn the git history into a readable book"
• "go commit by commit / PR by PR"
• "extract pivots, aha moments, pain points, and refactors"

The core problem is memory. Do not rely on the model remembering hundreds of commits. Externalize state early and keep it hierarchical.

Outcome

Produce a repository history "book" with: