Every repo has a trail.
Most people start at a random tree.
Open a big codebase and the first question is always the same: where do I even start? TrailHead answers it — paste a public GitHub repo and get a numbered reading path built from the repo's real import graph: README first, the entry point, the modules it actually pulls in, foundations before dependents, tests last. And an honest list of what to skip.
The URL swap
It works like GitDiagram — take any GitHub repo URL and swap the domain:
github.com/parthsingh03/AirGap → parthsingh03.github.io/TrailHead/parthsingh03/AirGap
No sign-up, no AI guessing — the order comes from imports, entry points and file links measured in the repo itself. Public repos only for now.
Fetching the repo…
The trail
Who uses whom
Each box is a source file; lines run from a file to the files it uses. Click a box to jump to its step on the trail.
The skip list ()
Files you can safely not read — knowing what to skip is half the trail.