Enforce Conventional Commits formatting for git commit messages.
npx skills add https://github.com/SaschaLeh/dotfiles --skill commit-saschaleh
Please help me install this Agent Skill. Skill: commit Source: https://github.com/SaschaLeh/dotfiles/tree/main/dot_claude/skills/commit Command: npx skills add https://github.com/SaschaLeh/dotfiles --skill commit-saschaleh
writing consistent commit messages helps teams understand history, reduces noise, and enables automated versioning and changelog generation. It enforces a standardized structure across commits to communicate intent, scope, and impact without reading full code changes.
Craft a conventional commit message for a new authentication feature.
High-intent search queries and answers about installing and using this skill.
To write a conventional commit message for breaking changes, add an exclamation mark before the colon, such as `feat(scope)!`, or include a `BREAKING CHANGE` footer in the commit body to clearly describe the impact.
The conventional commits specification standardizes git commit messages using structured types like feat and fix to communicate intent and scope, enabling automated versioning and changelog generation without requiring teams to read full code changes.
Format a scoped conventional commit by placing the scope in parentheses directly after the type, such as `feat(auth): add login validation`, to contextualize changes while keeping the description concise, imperative, and under 72 characters.
The conventional commits standard supports types including feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert to categorize the nature of code changes across a software project.
Yes, conventional commits works for automating release notes and changelogs because the standardized structure clearly distinguishes features, fixes, and breaking changes, allowing automated tools to parse history and generate version bumps accurately.
royhenengelGenerate conventional Git commit messages from staged code changes.
plurigridGenerate user-facing changelogs from git commit history.
kreuzberg-devEnforce Conventional Commits and pre-commit hooks for formatting, linting, and tests.
lushly-devGenerate Git commit messages following the Conventional Commits specification.
