Generate Conventional Commits 1.0.0 compliant Git commit messages from staged and unstaged changes.
npx skills add https://github.com/skilluse/skilluse --skill commit-skilluse
Please help me install this Agent Skill. Skill: commit Source: https://github.com/skilluse/skilluse/tree/main/.claude/skills/commit Command: npx skills add https://github.com/skilluse/skilluse --skill commit-skilluse
This Skill automates the generation of Git commit messages that adhere to the Conventional Commits specification, ensuring consistency and clarity in your project's commit history.
feat: commit message, and it will analyze the changes, suggest a type and scope, and format it correctly.Use the commit skill to generate a conventional commit message for the staged changes.
High-intent search queries and answers about installing and using this skill.
To generate conventional commit messages, this Skill analyzes your staged and unstaged git changes using `git status` and `git diff` to automatically determine the commit type, scope, and description.
The conventional commits format for breaking changes uses an exclamation mark `!` after the type or scope, or includes a `BREAKING CHANGE:` footer in the commit message body to clearly indicate the modification.
Yes, you can create specific git commit types. The Skill supports standard conventional commit types including `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, and `chore` based on your code changes.
Automated commit message generation analyzes code diffs by running `git status` and `git diff` to inspect your staged and unstaged changes, then inferring the appropriate conventional commit type and scope from the detected modifications.
You should stage files before generating a conventional commit. The Skill analyzes both staged and unstaged changes using `git status` and `git diff` to accurately formulate the commit type, scope, and description.
Using conventional commits instead of freeform git messages enforces a standardized format for types and scopes, which solves the problem of inconsistent commit history and improves project clarity and automated changelog generation.
RoentekStage the git working tree and generate a Conventional Commits message.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
hoangtran1411Enforce Conventional Commits and create semantic version tags with changelogs.
bswrundquistGenerate Git commit messages following the Conventional Commits specification.