Skip to content
Code Archaeology Read the codebase like a book. Argue with every chapter.

The books

Books are what you get when you run /dig against an open-source repo and edit the output for narrative. Each one is a chapter-by-chapter walkthrough of how the codebase actually got to its current shape — the team transitions, the rewrites, the incidents, the infamous decisions that turned out fine in the end.

Open an issue with the repo name and a one-liner on what makes its history interesting. Good candidates have:

  • 1000+ commits and 3+ years of history
  • Real PR discussions and meaningful commit messages
  • A story — team transitions, rewrites, controversies, incidents
  • An audience that would recognise the name on the cover

Or — better — point /dig at it yourself and send a PR with the chapters. Instructions in the README.