Validates conventional commit prefixes, scope, and message length in Git workflows.
npx skills add https://github.com/powdream/claude-plugins --skill commit-powdream
Please help me install this Agent Skill. Skill: commit Source: https://github.com/powdream/claude-plugins/tree/main/.claude/skills/commit Command: npx skills add https://github.com/powdream/claude-plugins --skill commit-powdream
This skill enforces consistent, conventional commit messages in Git-based workflows.
Create a conventional commit for a new feature in the authentication module, e.g., feat(auth): add login flow.
High-intent search queries and answers about installing and using this skill.
To enforce conventional commit messages in a Git workflow, you validate prefixes like feat:, fix:, and chore:, check scope usage, and verify message length to maintain repository consistency. This ensures changes are traceable and properly categorized.
Conventional commits are a standardized message format using prefixes like feat:, fix:, or docs: for version control. You need them in collaborative software projects to ensure every change is traceable and properly categorized for release notes.
Yes, you can use conventional commit validation in CI pipelines to automatically flag non-conforming messages. This validates message structure, scope usage, and prefixes during automated code reviews to maintain consistency across the repository.
To structure a conventional commit message for a multi-package repository, use a prefix followed by a scope, such as feat(auth): add login flow. This validates scope usage and categorizes changes to ensure they are traceable for release notes.
The best way to validate commit prefixes like feat: and fix: is to apply parsing rules that check for conventional-commit prefixes, validate scope usage, and enforce message length constraints. This flags non-conforming messages during code reviews.
Your commit message fails conventional commit rules if it lacks required prefixes like feat: or fix:, uses incorrect scope formatting, or exceeds message length limits. Enforcing these rules ensures consistency across collaborative software projects.
Marshall-HallenbeckGroup working-tree changes into conventional git commits with issue references.
plurigridGenerate user-facing changelogs from git commit history.
fworks-techValidate commit messages, PR titles, and branch health with commitlint and Husky.
vanman2024Standardize git workflows with commit templates, branch helpers, and hook scripts.
