I’ve been thinking about a simple problem:
We’re increasingly merging AI-assisted code into production, but we rarely preserve the thing that actually produced it — the session.
Six months later, when debugging or reviewing history, the only artifact left is the diff.
So I built git-memento.
It attaches AI session transcripts to commits using Git notes.
> the only artifact left is the diff
You also have code comments, docs in the repo, the commit message, the description and comments on the PR, the description and comments on your Issue tracker.
Providing context for a change is a solved problem, and there is relatively mature MCP for all common tooling.
loading story #47213744
The former GitHub CEO has a startup and this was their first release. They call it checkpoints: https://entire.io/
I copied it for my own tooling to make it work a bit better for my workflows.
loading story #47216093
A better solution would be to read and understand the code before committing it.
loading story #47215239
People won’t do that, unfortunately. We are a dying breed (I hate it). I went against my own instincts and vibe code this, works as a proof of concept.
You can see the session (including my typos) and compare what was asked for and what you got.
loading story #47213160
loading story #47213198
loading story #47213215
Capturing the AI session is practical for maintaining context during reviews. It will help when tracing back through history after the fact.
I already invented this in my head, thanks for not making me code it.
Excellent idea, I just wish GitHub would show notes. You also risk losing those notes if you rebase the commit they are attached to, so make sure you only attach the notes to a commit on main.
I added an action that will add a comment with the notes in GitHub so that you can see them directly.
I did work around squash to collect all sessions and concatenate them as a single one
loading story #47213811