The rise of AI-powered coding assistants has introduced a fascinating new question to our development workflow: if AI writes your code, should the conversation history be included in the commit?
At first glance, it sounds absurd. We don't commit our Google searches or Stack Overflow browsing history. But AI-assisted coding is fundamentally different. The prompt engineering, the back-and-forth refinement, the edge cases you discussed—these aren't just research. They're part of the design process.
Consider this: when reviewing a PR six months later, wouldn't it be valuable to see why the developer chose a particular approach? With traditional code, we rely on commit messages and code comments. But AI sessions often contain rich context—the constraints discussed, alternatives considered, and reasoning behind implementation choices.
Some developers are already experimenting with this. They're appending AI session summaries to commit messages or maintaining parallel documentation of significant AI interactions. Others argue it's noise—that code should speak for itself.
The truth likely lies somewhere in between. Not every AI interaction deserves preservation, but pivotal architectural decisions made through AI collaboration might warrant documentation. Think of it like pair programming notes: you don't transcribe every word, but you capture the key insights.
As AI becomes more integrated into our workflows, we'll need new conventions. Maybe a .ai-sessions/ directory? Commit message footers? Or perhaps IDE plugins that let you tag and archive significant interactions?
The conversation is just beginning, but one thing is clear: our version control practices need to evolve alongside our tools.
Also, if you want to check out my blogging project, visit Pluma.ink - a clean platform for documenting ideas.
Top comments (0)