This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Commit Intent
Pre-commit hook that writes an intent doc by mining AI chats
Git records what changed, not why. When AI writes a 300-line diff, the reasoning, constraints, and decisions stay behind in chat logs on your disk. That's the newest technical debt: lost context. At commit time, it matches session transcripts to your staged files and uses the Claude Code CLI you already have to distill the intent into docs/intents/, staged into the same commit as the code it explains. The why travels with the what. No new platform, no new workflow, no commit ever blocked.
Hey Product Hunt! 👋
Adrian here. This came out of pure frustration: I'd open a file Claude Code wrote three weeks ago, have zero memory of why it handled an edge case that way, and know the answer was sitting in a chat transcript somewhere on my disk. Git blame told me nothing. The AI that wrote it couldn't remember either.
So I built the smallest possible fix: at commit time, match the session transcripts to the staged files, distill the intent into a markdown doc, and commit it alongside the code. No new platform, no workflow change. It uses the Claude Code CLI you already have installed.
A few honest notes:
It only helps if you code with AI in sessions it can find. Hand-typed hotfixes just pass through.
The intent docs are only as good as the distillation, so I'd genuinely love examples where it got the "why" wrong.
Biggest question I'm wrestling with: should the intent doc live separately from the planning doc used to generate the code? Curious what this community thinks.
Thanks for checking it out!
About Commit Intent on Product Hunt
“Pre-commit hook that writes an intent doc by mining AI chats”
Commit Intent was submitted on Product Hunt and earned 6 upvotes and 3 comments, placing #145 on the daily leaderboard. Git records what changed, not why. When AI writes a 300-line diff, the reasoning, constraints, and decisions stay behind in chat logs on your disk. That's the newest technical debt: lost context. At commit time, it matches session transcripts to your staged files and uses the Claude Code CLI you already have to distill the intent into docs/intents/, staged into the same commit as the code it explains. The why travels with the what. No new platform, no new workflow, no commit ever blocked.
On the analytics side, Commit Intent competes within Software Engineering, Artificial Intelligence, GitHub and Vercel Day — topics that collectively have 557.9k followers on Product Hunt. The dashboard above tracks how Commit Intent performed against the three products that launched closest to it on the same day.
Who hunted Commit Intent?
Commit Intent was hunted by Adrian Bunge. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Commit Intent including community comment highlights and product details, visit the product overview.
Adrian Bunge