Commit Message Analyzer
Paste up to 10 commit messages. We'll tell you which are marketable.
Analyzing your commits...
Analysis Summary
0% of your commits are marketable
Unlock Your Full Analysis
Get a detailed PDF breakdown of each commit with improvement suggestions.
Related Guides
Frequently Asked Questions
What is a marketable commit?
A marketable commit is a code change that customers care about—new features, bug fixes, UI improvements, or performance gains. Internal commits like refactoring, tests, or build config changes typically don't belong in customer-facing release notes.
How do I write better commit messages for release notes?
Start with a verb (add, fix, improve), describe what changed from the user's perspective, and keep it under 72 characters. For example: "Add dark mode toggle to settings" instead of "refactor theme handling code".
What's the difference between customer-facing and internal commits?
Customer-facing commits directly impact the user experience: new features, bug fixes users encounter, UI changes, and noticeable performance improvements. Internal commits include refactoring, tests, CI/CD changes, dependency updates, and code cleanup.
How many commits should I include in release notes?
Focus on 5-15 customer-facing commits per release. Group related changes together and translate technical language into benefits. Quality over quantity—readers skim release notes, so highlight the most impactful changes.