Validate commit messages against the Conventional Commits specification.
npx skills add https://github.com/matteing/opal --skill git-matteing
Please help me install this Agent Skill. Skill: git Source: https://github.com/matteing/opal/tree/main/.claude/skills/git Command: npx skills add https://github.com/matteing/opal --skill git-matteing
Enforcing a strict conventional commit format prevents inconsistent commit messages, messy changelogs, and incorrect semantic version bumps, making releases and code review clearer and more automatable.
Create a conventional commit message for a bug fix in the core module with the description prevent crash when tool returns empty response.
High-intent search queries and answers about installing and using this skill.
Use conventional commit validation to require a type, optional scope, and lowercase imperative description. This ensures uniform conventional commits and enables predictable changelog generation and semantic versioning.
A conventional commit message with a breaking change requires a type, optional scope, lowercase imperative description, and a breaking change marker. The format includes specific body and footer formatting to signal semantic versioning bumps.
Structure a conventional commit for a core module bug fix by using the fix type with core as the scope, followed by a lowercase imperative description. An example is: fix(core): prevent crash when tool returns empty response.
Semantic versioning maps conventional commit types to version bumps. By enforcing strict commit message formats with validated types and scopes, release workflows can automatically determine major, minor, or patch version increments.
Pull request commits fail automated release workflow checks when conventional commit messages lack required types, scopes, or lowercase imperative descriptions. Validating one logical change per commit ensures CI release steps and changelog generation work reliably.
You need conventional commits for git history hygiene when preparing pull requests or managing changes across core, cli, rpc, agent, tools, and release workflows. Enforcing this format ensures one logical change per commit and automatable code reviews.
wesleyosantos91Generate Conventional Commits messages from git diffs with type and scope.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
laozhong86Enforce atomic commits with GXPM-N messages and pre-commit hook checks.
vulikjulikGenerate conventional commit messages from staged git changes.
