Skill Detail

Generate and validate conventional commits and semver release bumps with Commitizen

<p>Standardize commit messages, validate commit history, and calculate semver-aware release bumps without hand-rolled repo rules.</p>

Templates & WorkflowsMulti-Framework
Templates & Workflows Multi-Framework Published
⭐ 3.4k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill generate-and-validate-conventional-commits-and-semver-release-bumps-with-commitizen Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Git, Python 3.9+, and the Commitizen CLI in a repository with a defined commit convention.
Install & setup
<p>Install with <code>pip install -U commitizen</code> or your preferred Python environment manager, add Commitizen configuration in <code>pyproject.toml</code>, <code>.cz.toml</code>, or equivalent, then run commands such as <code>cz commit</code>, <code>cz check</code>, and <code>cz bump</code> inside the target repository.</p>
Author
commitizen-tools
Publisher
Organization
Last updated
Apr 17, 2026
Quick brief

Use Commitizen when an agent needs to create or validate Conventional Commit messages, check a repository’s commit history against an agreed convention, and drive semver-aware version bumps from those commits. It fits release prep, changelog generation, and repo-hygiene workflows where commit semantics need to stay consistent across many edits.

How it works

What this skill actually does

A user should invoke this instead of using Git or a release tool normally when the task is commit convention enforcement and release bump orchestration, not everyday branching or publishing itself. The scope boundary is narrow and skill-shaped: Commitizen governs commit structure, changelog-friendly history checks, and calculated version bumps, not generic Git hosting, CI, or package registry management.