Dev
Fake Commit Message Generator
Used by developers, writers, and creators worldwide.
A fake commit message generator produces realistic conventional-commit messages for seeding test repositories, demos, and screenshots. When you need a git history that looks real — for a tutorial, a tool demo, or test fixtures — random lorem text looks wrong; commit messages have a distinct shape. This tool generates messages in the conventional-commits format (type, scope, and description), like "feat(auth): add pagination to the results list," so your fake history reads like a real project's. Choose how many you need and copy the batch. It is ideal for developers demoing git tools, writing tutorials, or seeding test data for changelog and CI scripts. The messages are fictional but well-formed, so they also serve as handy examples when teaching the conventional-commits convention to a team.
Loading usage…
Free forever — no account required
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Choose how many commit messages you want.
- Click Generate to produce conventional commits.
- Copy them into your test repo or demo.
- Adapt scopes and descriptions to fit your project.
Use Cases
- •Seeding a test git repository with history
- •Demoing a git or changelog tool
- •Realistic commit messages for screenshots
- •Test fixtures for CI and changelog scripts
- •Teaching the conventional-commits format
Tips
- →Match scopes to your project's real modules.
- →Use a consistent type vocabulary across the team.
- →Great for seeding changelog-tool demos.
- →Pair with a fake-git-commit generator for full commits.
FAQ
what is the conventional commits format
Conventional Commits structure a message as type(scope): description — for example feat(api): add rate limiting. The type (feat, fix, docs, etc.) and optional scope make history easy to scan and enable automated changelog and version tooling.
why use fake commit messages
They let you seed a realistic git history for demos, tutorials, screenshots, and test fixtures without inventing each message by hand. Well-formed messages look far more convincing than random text when you are showing off a tool.
are these based on real commits
No — they are randomly assembled from common types, scopes, and descriptions. They are fictional but follow the conventional-commits convention, so they look authentic and also work as teaching examples for the format.