If AI writes code, should the session be part of the commit?

Proof sketch is not proof

This would just record a lot of me cursing at and calling the AI an idiot.

Like any discussion about AI there are two things people are talking about here and it's not always clear which:

1. Using LLMs as a tool but still very much crafting the software "by hand",

2. Just prompting LLMs, not reading or understanding the source code and just running the software to verify the output.

A lot of comments here seem to be thinking of 1. But I'm pretty sure the OP is thinking of 2.

Yes.

EOM

No. Prompt-like document is enough. (e.g. skills, AGENTS.md)

I feel like publishing the session is like publishing a sketch book. I don't need all of my mistakes and dumb questions recorded.

If that was important, why are we not already doing things like this. Should I have always been putting my browser history in commits?

I include my "plans" and a link to my transcript on all my PRs that include AI-generated code. If nothing else, others on my team can learn from them.

I've thought about this, and I do save the sessions for educational purposes. But what I ended up doing is exactly what I ask developers to do: update the bug report with the analysis, plan, notes etc. In the case there's a single PR fixing one bug, GitHub and Claude tend to prefer this information go in the PR description. That's ok for me since it's one click from the bug.

obligatory: git notes

Lots of comments mentioned this, for those who aren't aware, please checkout

Git Notes: Git's coolest, most unloved­ feature (2022)

https://news.ycombinator.com/item?id=44345334

I think it's a perfect match for this case.

I must say that would certainly show some funny converstaions in a log.

no and neither should be the actual code. you should at least remove the excessive bs that the ai comments and autisms about

nope. Someones going to leak important private data using something like this.

Consider:

"I got a bug report from this user:

... bunch of user PII ..."

The LLM will do the right thing with the code, the developer reviewed the code and didn't see any mention of the original user or bug report data.

Now the notes thing they forgot about goes and makes this all public.

[dead]

[dead]

[dead]

[dead]