If AI writes code, should the session be part of the commit?
3 points
1 hour ago
| 3 comments
| github.com
| HN
danhergir
1 hour ago
[-]
One of the use cases i see for this tool is helping companies to understand the output coming from the llm blackbox and the process which the employee took to complete a certain task
reply
mandel_x
1 hour ago
[-]
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.
reply
latexr
1 hour ago
[-]
A better solution would be to read and understand the code before committing it.
reply
mandel_x
1 hour ago
[-]
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.

reply
ares623
50 minutes ago
[-]
Maybe Git isn't the right tool to track the sessions. Some kind of new Semi-Human Intelligence Tracking tool. It will need a clever and shorter name though.
reply