Write commit messages following the Conventional Commits specification.
npx skills add https://github.com/jmreicha/lazycfg --skill commit-jmreicha
Please help me install this Agent Skill. Skill: commit Source: https://github.com/jmreicha/lazycfg/tree/main/.claude/skills/commit Command: npx skills add https://github.com/jmreicha/lazycfg --skill commit-jmreicha
Inconsistent commit messages make it hard to understand project history, complicate changelogs, and hinder automated release processes.
Use the conventional commits format to craft a clear commit message for the next change, e.g., feat(auth): add login capability.
High-intent search queries and answers about installing and using this skill.
A conventional commit message follows a specification defining type, scope, and description formatting. You need conventional commits to standardize project history, enable reliable changelogs, and support automated release processes across software workflows.
To write a conventional commit message, structure it with a type, optional scope, and descriptive message. For example, use feat(auth): add login capability for features, or fix(api): resolve timeout error for bug fixes, applying best-practice templates.
Conventional commits support PR reviews and changelogs by enforcing standardized type, scope, and description formatting. This consistent structure enables reliable release notes generation and allows automation tools to parse breaking changes and project history accurately.
To indicate a breaking change in a conventional commit, apply the specification's breaking-change handling guidelines within the optional body or description formatting. This ensures automated release processes correctly detect and document the breaking change.
Yes, you can use conventional commits across different software projects, teams, and workflows. The specification provides guidelines and best-practice templates that help teams adopt consistent patterns for features, fixes, docs, and chores regardless of project context.
Inconsistent git workflow documentation complicates version control because irregular commit messages make it hard to understand project history, hinder automated release processes, and complicate changelog generation across software projects.
armanzeroeightGenerates commit messages from git diff output with customizable Type and Scope options.
plurigridGenerate user-facing changelogs from git commit history.
rnavarychGuide Git branching, commit conventions, and pull request workflows.
JsplixGenerate standardized conventional commit messages for the AX-WMS monorepo.
