Write commit messages following the Conventional Commits specification.
npx skills add https://github.com/jrodrigopuca/skills --skill using-commit
Please help me install this Agent Skill. Skill: using-commit Source: https://github.com/jrodrigopuca/skills/tree/main/using-commit Command: npx skills add https://github.com/jrodrigopuca/skills --skill using-commit
This Skill helps you write clear, consistent, and machine-readable commit messages that improve project history and enable automation.
feat(scope): description format, including a breaking change notice if necessary.Use the using-commit skill to write a commit message for adding a new user authentication feature.
High-intent search queries and answers about installing and using this skill.
To write conventional commit messages for automated changelog generation, structure your commits using the feat, fix, or other type prefixes with an optional scope, like feat(scope): description, to ensure a clear, machine-readable history. This enables tools to automatically generate changelogs and manage semantic versioning.
The conventional commits specification format for breaking changes requires adding a ! after the type or scope, or including a BREAKING CHANGE footer. This structured format ensures automated tools can detect breaking changes and properly increment the major semantic version number.
To structure git commit messages for features and fixes, use the feat type for new functionality and fix for bug corrections, followed by an optional scope in parentheses and a clear description. This standardization facilitates automated semantic versioning and changelog generation.
Yes, you can use conventional commits to automate semantic versioning. By adhering to the specification with structured types like feat and fix, tools can parse your machine-readable history to automatically determine and apply the correct version bumps.
Best practices for machine-readable git commit history involve strictly following the conventional commits specification, using defined types, scopes, and breaking change notices. This structured approach improves project history clarity and enables automated changelog generation and semantic versioning.
KibertumAnalyze diffs and generate conventional git commit messages with pre-commit checks.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
drgaciwGenerate changelogs and release notes from Conventional Commits in CI/CD pipelines.
buiminhduc23011Standardize git commit messages using type(scope): description format.