Why does this
code exist?
Every codebase carries decisions nobody documented. Vestige reads your Git history to surface the why behind every change.
How it works
Ingest
Point Vestige at any Git repo. It reads your full commit history, diffs, PRs, and branch patterns — everything your team left behind.
Trace
Every change is traced back to its origin. Vestige surfaces the decision, the context, and the confidence level of each inference.
Explain
Claude turns the evidence into a narrative tailored to whoever is reading so the why reaches everyone who needs it.
From a commit with no message
to a reason.
add null check
a3f9c2b · auth/parseToken.ts
update validation
b81e04a · auth/validateUser.ts
fix
c29f17d · middleware/auth.ts
A null check was added to parseToken(), a type guard was introduced in validateUser(), and an error catch was wrapped around the middleware call — the pattern of these three changes together is consistent with a runtime crash on an unexpected null return.
⚠ No incident report found. Decision inferred from history.
Vestige gives you the story of how your codebase evolved to what it is today.
But history can't tell you the safest place to put your next change.
That's why we built Placement.
Feel confident where you put your code won't
break anything.
I want to add a hover state for .card-title that changes the color to the brand purple.
Add after line 827, directly below .card-title — this is where component-level states live in this file. Adding here keeps it out of the global reset block above and the utility classes below.
→ Safe. Follows the file's own pattern.
This section is under construction
features.
Why is this like this?
Read the full commit history, PRs, and branch patterns. Claude writes you the story of every decision — documented and inferred.
Where does my change belong?
Point Vestige at a file and describe what you're adding. It reads the structure and tells you the exact line — and why that placement is safe.
When your working in a codebase you didn't write. Vestige answers both, in order, and gets out of your way.
Above under construction
Every codebase has a history.
Now you can read it.
Every weird architectural choice, every quiet dependency swap, every late-night hotfix and now, every change you make — placed with confidence.