CHAPTER 01
Connect a repository
Authorize read-only access to one repository. Maulwurf builds the initial index — git history, source files, docs — which usually takes minutes, not hours. You'll get a ping when the first dig is ready.
Tip: start with the repository nobody fully understands. That's where the value lives.
CHAPTER 02
Ask your first question
Ask in plain language, the way you'd ask a senior engineer:
Where does the auth token refresh happen?Who owns the billing module?Why does checkout fail for EU users?
Specific questions dig better than vague ones. "How does X work" beats "explain the codebase".
CHAPTER 03
Verify the citations
Every answer carries citations: file, line, and commit. Click through to the first few — build the habit of verifying before trusting. If a citation looks off, tell us; it makes the digger better.
Tip: uncertain answers are a feature, not a bug. They mark exactly where your documentation has gaps worth filling.
CHAPTER 04
Dig deeper
- Follow up in the same thread — context carries over.
- Ask "why" questions against git history, "where" questions against source.
- Connect related repos to answer cross-service questions.
- Re-index after big refactors so answers stay fresh.