Generate conventional commit messages with type, scope, and description.
npx skills add https://github.com/PacificStudio/openase --skill commit-pacificstudio
Please help me install this Agent Skill. Skill: commit Source: https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/commit Command: npx skills add https://github.com/PacificStudio/openase --skill commit-pacificstudio
This skill helps developers produce concise Conventional Commit messages that accurately reflect the scope of code changes, improving project history readability and tooling integration.
Provide a concise conventional commit message that matches the scope of the change.
High-intent search queries and answers about installing and using this skill.
Conventional commit messages require a type, optional scope, and concise description to accurately reflect code changes. This format applies to features, fixes, refactors, and tests, ensuring project history readability and tooling integration.
A commit scope is an optional identifier in conventional commits specifying the section of codebase affected. You include it to maintain consistent commit history across releases and clarify the impact of features, fixes, or refactors.
To generate a git commit message for a bug fix, use the fix type with an optional scope and a concise description. This enforces the Conventional Commits format, accurately reflecting the scope of the code change.
Yes, the conventional commits format works for refactoring and adding new features. You apply the appropriate type, such as feat or refactor, with an optional scope and descriptive message to accurately represent the code change.
The best way to maintain consistent commit history is enforcing the Conventional Commits structure with a clear type, optional scope, and descriptive message. This guides developers to select appropriate scopes for all project changes.
Conventional commits improve project history readability and tooling integration compared to plain text. By enforcing a structure with type, optional scope, and description, they accurately reflect the scope of code changes for features, fixes, and refactors.
LuminairPrimeGenerate conventional commit messages from analyzed git staged changes.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
iowarpProvide contribution guidelines for the IOWarp/Clio ecosystem covering Git workflow and C++ standards.
nilleReview code diffs for correctness, security, and conventions.
