Enforce conventional commit syntax with type, scope, and subject.
npx skills add https://github.com/alkofu/ai-tpk --skill commit-message-guide-alkofu
Please help me install this Agent Skill. Skill: commit-message-guide Source: https://github.com/alkofu/ai-tpk/tree/main/claude/skills/commit-message-guide Command: npx skills add https://github.com/alkofu/ai-tpk --skill commit-message-guide-alkofu
Commit messages are often terse, inconsistent, and hard to parse during reviews and changelogs, making it difficult to track changes over time. This skill guides teams to write clear, conventional commits that convey intent and scope.
Draft a commit using the conventional format: <type>(<scope>): <subject>.
High-intent search queries and answers about installing and using this skill.
Conventional commit messages use the syntax <type>(<scope>): <subject> to standardize code changes. This structure defines allowed types like feat or fix, applies optional body and footer information, and conveys clear intent during version control workflows.
Allowed types in the conventional commits style guide include feat, fix, refactor, perf, style, test, docs, build, ci, and chore. These types standardize the required syntax and help teams track changes over time during code reviews and changelog generation.
Include an optional body and footer in a commit message to capture rationale and breaking changes. This best practice supplements the required <type>(<scope>): <subject> syntax, providing additional context for team collaboration and release processes.
Yes, the conventional commit format enforces consistent, descriptive commit messages that are easily parsed for changelog generation. Standardizing type, scope, and subject allows automated tools to track changes during development and release processes.
The best way to standardize inconsistent git commit messages is enforcing a conventional commit structure with defined syntax and recommended practices. This approach constrains required types and scopes, making code changes easy to parse during reviews.
You should use a scope in your conventional commit subject to specify the module or component affected by the code change. This descriptive practice supplements the required type and subject format, improving team collaboration and tracking.
Fandry96Stage changes, generate conventional commits, and push to a remote Git repository.
plurigridGenerate user-facing changelogs from git commit history.
HorusGoulGenerate Git commit messages from session history using conventional commit syntax.
gaia-iaGenerate conventional commit messages from staged Git diffs.
