Generator wiadomości Git commit — Darmowe narzędzie online

Git Commit Message Generator -- Conventional Commits Made Easy

The Narzędzieolis Git Commit Message Generator builds properly formatted commit messages following the Conventional Commits specification, Angular commit conventions, or a simplified format. Fill in the type, scope, and description, preview the result, and copy it to your clipboard -- no more guessing whether to use "feat" or "fix", or forgetting the breaking change footer format.

Why commit message format matters

A well-formatted commit history is more than just good hygiene. It enables powerful automation: tools like semantic-release can automatically bump versions and generate changelogs by parsing commit types. feat triggers a minor bump, fix triggers a patch, and BREAKING CHANGE triggers a major version. Teams that adopt Conventional Commits spend less time debating commit message style and more time shipping code.

The Conventional Commits specification

The Conventional Commits spec defines a structured format for commit messages:

• type(scope): description -- the subject line (max 72 chars)
• A blank line separates the subject from the body
• The body explains "why" the change was made, not "what" changed (the diff shows that)
• BREAKING CHANGE: description as a footer signals incompatible changes
• A ! after the type/scope is a shorthand for breaking changes: feat!: remove legacy API

Commit types explained

• feat -- introduces a new feature visible to end users
• fix -- patches a bug in existing functionality
• docs -- changes to documentation only (README, API docs, comments)
• style -- code formatting, whitespace, semicolons -- no logic change
• refactor -- code restructuring without changing external behavior
• perf -- performance improvements (faster queries, less memory)
• test -- adding or updating tests, no production code change
• chore -- tooling, configs, dependency updates, CI tweaks
• build -- changes to the build system (webpack, vite, esbuild)
• ci -- CI/CD pipeline configuration (GitHub Actions, Jenkins)

Format comparison

This tool supports three output formats:

• Conventional Commits -- the industry standard: feat(auth): add SSO support
• Angular -- the original convention that inspired Conventional Commits, identical structure but includes build and ci types
• Simple -- just the description with optional scope in brackets: [auth] Add SSO support

Integrations and tooling

Conventional Commits unlock a rich ecosystem of tools:

• semantic-release -- fully automated version management and changelog generation
• commitlint -- lint commit messages in CI to enforce the convention
• commitizen -- interactive CLI wizard for writing commits (this tool is the browser equivalent)
• standard-version -- changelog generation from commit history
• git-cliff -- highly customizable changelog generator

Writing better commit descriptions

• Use imperative mood -- "add", not "added" or "adds". Complete the sentence: "This commit will..."
• Keep it under 72 characters -- fits in terminal, GitHub truncates at ~72
• Nie period at the end -- the subject line is a title, not a sentence
• Lowercase first letter -- Conventional Commits convention (though not strictly required)
• Reference issues -- "Closes #42", "Fixes #108" for automatic issue closing