Need AI Training/Help?CloudYeti.io/meet
MarkdownMe
Developer commit guide

AI Coding Session Commit Message Generator

Turn a Claude Code, Codex, Cursor, Copilot, or Windsurf coding session summary into one clean Conventional Commit message.

Direct answer

For an AI coding session, write the commit around the one logical change the diff delivers, not every file the assistant touched. Summarize the user-visible outcome, choose the Conventional Commit type from that outcome, add a scope if one subsystem dominates, and keep implementation details in the body only when they help reviewers understand the change.

Open Conventional Commit Generator

When to use this

  • Claude Code, Codex, Cursor, Copilot, or Windsurf changed multiple files.
  • The implementation is noisy but the user-facing change is one logical unit.
  • You want a commit message that release automation and reviewers can understand.

Steps

  1. Paste the AI session summary, final diff summary, or PR notes.
  2. Identify the single outcome that should appear in history.
  3. Choose the Conventional Commit type from that outcome.
  4. Use a short scope such as auth, api, docs, quiz, or deploy when helpful.
  5. Put noisy file-level details in the body only if they explain risk or review context.

Example

Change context
Codex added resume diagnostic state persistence, a resume card, GA4 event tracking, and tests. Users who leave the public quiz can continue from the next unanswered question.
Commit message
feat(quiz): resume public diagnostics from saved progress

Common mistakes

  • Do not mention the assistant name in the subject unless the change is about the assistant integration itself.
  • Do not create one commit type per file if the work is one logical feature or fix.
  • Do not hide breaking behavior just because the change came from an AI session.

FAQ

Should the commit say Claude Code or Codex did the work?
Usually no. The commit subject should describe the product or code change. Mention the assistant only if the feature itself is about that assistant.
What if the AI session made unrelated changes?
Split unrelated changes into separate commits before generating messages, then write one Conventional Commit per logical unit.
Can I paste a git diff into the generator?
You can paste a concise diff summary or selected context. The tool works best when you describe what changed and why instead of pasting a huge raw diff.

Related Conventional Commit guides

Which Conventional Commit Type Should I Use?

Choose the right Conventional Commit type for feat, fix, docs, refactor, perf, test, build, ci, chore, and revert commits.

Fix a Commitlint Conventional Commit Failure

Rewrite failed commitlint subjects into valid Conventional Commit messages with the right type, scope, subject, and breaking-change footer.

Semantic Release Conventional Commit Version Bump

Use Conventional Commits to signal patch, minor, and major releases for semantic-release, release-please, changesets, and similar tooling.