Validate commit messages against the Conventional Commits specification.
npx skills add https://github.com/oimiragieo/LLM-RULES --skill commit-validator
Please help me install this Agent Skill. Skill: commit-validator Source: https://github.com/oimiragieo/LLM-RULES/tree/main/.claude/skills/commit-validator Command: npx skills add https://github.com/oimiragieo/LLM-RULES --skill commit-validator
Programmatically validates commit messages against the Conventional Commits specification, providing instant feedback during development.
Validate commit message: feat(auth): add OAuth2 login support
High-intent search queries and answers about installing and using this skill.
Conventional Commits validation enforces a standardized message format: <type>(<scope>): <subject>. Allowed types are feat, fix, docs, style, refactor, perf, test, chore, ci, build, and revert. The subject must be imperative, lowercase, without a period. The Skill parses your commit message and returns structured results showing validity, type, scope, and any errors or warnings.
Yes. Commit validation works before commits locally via pre-commit hooks, in CI/CD pipelines to enforce team standards, and during code reviews. This catches non-conforming messages early, preventing inconsistent commit history across your project.
Conventional Commits requires the header format <type>(<scope>): <subject>, where type is mandatory (feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert), scope is optional, and subject must be imperative and lowercase without a trailing period. Body and footer sections are allowed after a blank line.
Standardized commit messages via Conventional Commits make your project history readable, enable automated changelog generation, and improve collaboration. The Skill validates messages consistently across development, pre-commit stages, and CI pipelines, ensuring all contributors follow the same format.
The validator returns a structured result containing the parsed type, scope, subject, a validity flag, and any warnings or errors encountered. This structured feedback lets you programmatically handle validation results in hooks, pipelines, and code review workflows.
Yes. Commit validation integrates into existing git workflows through pre-commit hooks, CI/CD pipelines, and manual code review processes. It requires no changes to your repository structure and returns results that fit into any automation or review system.
abonetoAutomatically stage and commit changes after Spec Kit hook events.
whitebearditValidate commit messages and PR titles against Conventional Commits rules.
adelproEnforce conventional commits, branch naming, PR etiquette, and release tagging.
allanninalConvert git commits into changelogs following Keep a Changelog and Conventional Commits.
