Code Archaeologist

function → commit → PR → issue

Trace the why behind your code

Not semantic search.
Sourced evidence chains.

Connect a GitHub repo, ingest its code history and PR/issue context into a Cognee knowledge graph, then ask why any function exists — with citations that link to real commits, pull requests, and issues.