Format Git commit messages with HyperShift conventional commit rules.
npx skills add https://github.com/czyt/claude-skills --skill git-commit-format-czyt
Please help me install this Agent Skill. Skill: Git Commit Format Source: https://github.com/czyt/claude-skills/tree/main/skills/git-commit-format Command: npx skills add https://github.com/czyt/claude-skills --skill git-commit-format-czyt
This Skill enforces a consistent and standardized format for Git commit messages, improving code review clarity and automated changelog generation.
Signed-off-by and Commit-Message-Assisted-by.gitlint validation.feat(<scope>): <description> format and includes all required footers.Use the Git Commit Format skill to generate a commit message for a new feature that adds user authentication.
High-intent search queries and answers about installing and using this skill.
To format Git commit messages for automated changelog generation, apply conventional commit rules using a structured format with type, scope, and description. This Skill enforces these standards along with mandatory footers like Signed-off-by to ensure parsing consistency.
The required footers in a conventional commit message are Signed-off-by and Commit-Message-Assisted-by. This Skill enforces the inclusion of these mandatory footers alongside the structured type, scope, and description to meet HyperShift formatting rules.
To indicate a breaking change in a Git commit message, use the '!' symbol after the type and scope or add a BREAKING CHANGE footer. This Skill supports both methods to clearly flag modifications that break backward compatibility.
Yes, gitlint validates the title and body line length of commit messages. This Skill enforces these gitlint validation rules to ensure your commit message structure adheres to specified length constraints and formatting guidelines.
Yes, you can use this conventional commit format for adding a new feature by following the feat(<scope>): <description> structure. The Skill ensures your commit message includes the correct type, scope, and required footers for feature additions.
Git commit messages fail code review formatting checks when they lack a structured type, scope, mandatory footers like Signed-off-by, or exceed gitlint line length limits. This Skill applies HyperShift conventional commit rules to validate and correct these structural issues.
nvimcraftGenerate Angular Conventional Commit messages from staged Git changes.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
nicolanoviellReview code changes for bugs, style issues, and best practices.
alexandremendoncaalvaroDraft atomic Conventional Commits with DCO Signed-off-by sign-off.