Commit Message Generator

The problem

Vague commit messages like "fix stuff" or "updates" make git histories unreadable and break automated changelog tools. Manually formatting conventional commits is repetitive and prone to small syntax errors like trailing periods or wrong tense.

What it does

• Standardizes code changes into the conventional commit format: type, scope, and subject.
• Maps your change descriptions to the correct type like feat, fix, docs, or refactor.
• Enforces imperative mood for subjects to keep the history professional.
• Drafts optional body content that explains the reasoning behind a change rather than just the code diff.

Why this beats prompting it yourself

This skill eliminates the need to remember specific type categories or syntax rules every time you commit. It handles the cognitive load of phrasing subjects imperatively and structuring the scope, ensuring your entire team's history remains perfectly scannable for CI/CD pipelines.

Use cases

• Generating structured messages for automated semantic versioning tools.
• Standardizing commit history across a multi-developer team.
• Writing clear explanations for complex architectural refactors.
• Quickly tagging chore or CI tasks without breaking flow.

Known limitations

Requires a clear text description of the change as it cannot view your local source code. Follows standard Conventional Commits and may need manual adjustment for custom team formats.