I used to spend extra time writing detailed comments in my Git commits.

Not just about what changed, but why — so my team could learn from the reasoning behind my code. It also serves as a reference for my future self.

1 min read LinkedIn
I used to spend extra time writing detailed comments in my Git commits.

Not just about what changed, but why — so my team could learn from the reasoning behind my code. It also serves as a reference for my future self.

Fast forward to today.

Most of my code is written with AI now. I now add the prompts I used as comments in my Git commits. That way, it doesn’t just record the code changes — it records the conversation that shaped it.

Sometimes, when I use Gemini to recall the prompts from a coding session, it even shows me the initial prompt that Gemini CLI sends to the LLM. Like catching a glimpse behind the scenes of how it works.

To me, Git commits are no longer just about documenting code. They’re becoming a record of collaboration with AI.

And here’s another thought. This evolving Git history — code plus prompts — could become valuable training data to improve the next generation of coding LLMs.

What do you think? Do you add your prompts to your Git commits?

I share practical tips about business, marketing and AI

🔔 Follow me to learn more!

♻️ Re-post this to help others!

🔖 Save this for future reference!

💬 DM me for collaboration!

#GenAI #SoftwareDevelopment #Git #Coding #VibeCoding

Enjoyed this? Subscribe for more.

Practical insights on AI, growth, and independent learning. No spam.

More in Vibe Coding