React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…
Install Commitizen
$ npx skills add commitizen-tools/commitizen --skill commitizen -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install commitizen-tools/commitizen commitizen --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/commitizen-tools/commitizen.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/commitizen .claude/skills/commitizen && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "commitizen" agent skill from https://github.com/commitizen-tools/commitizen/tree/master/.agents/skills/commitizen into .claude/skills/commitizen/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commitizen", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/commitizen-tools/commitizen/tree/master/.agents/skills/commitizenType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add commitizen-tools/commitizen --skill commitizen -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install commitizen-tools/commitizen commitizen --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/commitizen-tools/commitizen.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/commitizen .agents/skills/commitizen && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "commitizen" agent skill from https://github.com/commitizen-tools/commitizen/tree/master/.agents/skills/commitizen into .agents/skills/commitizen/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commitizen", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add commitizen-tools/commitizen --skill commitizen -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install commitizen-tools/commitizen commitizen --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/commitizen-tools/commitizen.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/commitizen .cursor/skills/commitizen && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "commitizen" agent skill from https://github.com/commitizen-tools/commitizen/tree/master/.agents/skills/commitizen into .cursor/skills/commitizen/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commitizen", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/commitizen-tools/commitizen.git --path .agents/skills/commitizen--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add commitizen-tools/commitizen --skill commitizen -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install commitizen-tools/commitizen commitizen --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/commitizen-tools/commitizen.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/commitizen .gemini/skills/commitizen && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "commitizen" agent skill from https://github.com/commitizen-tools/commitizen/tree/master/.agents/skills/commitizen into .gemini/skills/commitizen/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commitizen", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install commitizen-tools/commitizen commitizenInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add commitizen-tools/commitizen --skill commitizen -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/commitizen-tools/commitizen.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/commitizen .github/skills/commitizen && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "commitizen" agent skill from https://github.com/commitizen-tools/commitizen/tree/master/.agents/skills/commitizen into .github/skills/commitizen/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commitizen", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add commitizen-tools/commitizen --skill commitizen -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install commitizen-tools/commitizen commitizen --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/commitizen-tools/commitizen.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/commitizen .opencode/skills/commitizen && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "commitizen" agent skill from https://github.com/commitizen-tools/commitizen/tree/master/.agents/skills/commitizen into .opencode/skills/commitizen/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commitizen", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
commitizen- GitHub stars
- 3.5k
- Token cost
- ~839 tokens
- SKILL.md length
- 378 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…
- Works in 7 steps: Find the active configuration file in… → Read the effective settings before… → Match the command to the task → …
- Tasks involving Conventional Commits
- SKILL.md covers Use this skill when, Core workflow, Important domain details and Examples
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Commitizen is an agent skill from commitizen-tools/commitizen. Use this skill for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the Commitizen CLI.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Commit messages and Changelog and release notes. It works with Python and Git. The repository describes itself as: Create committing rules for projects :rocket: auto bump versions :arrowup: and auto changelog generation :openfilefolder:. The licence is MIT.
When your agent uses it
- Tasks involving Conventional Commits
- Commit message validation
- Commitizen configuration
- Semantic version bumps
Example prompts
- “/commitizen”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Find the active configuration file in this order: .cz.toml, cz.toml, .cz.json, cz.json, .cz.yaml, cz.yaml, then pyproject.toml under…
- Read the effective settings before acting, especially name, version, version_provider, version_scheme, version_files, tag_format…
- Match the command to the task
- Prefer read-only inspection first. Safe discovery commands include cz version, cz ls, cz check, cz bump --get-next, and cz bump --dry-run.
- Treat cz bump as stateful: it can update version files, create a bump commit, and create a git tag. Verify the version provider, version…
- When automating in CI, check whether the workflow should ignore specific exit codes with --no-raise and whether bump_message should…
- After making changes, validate the resulting configuration, commands, and automation against the repository's actual version scheme and…
What it can do on your machine
Read from SKILL.md and the folder at commit 2f86834. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Commitizen loads about 839 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 378 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from commitizen-tools/commitizen at commit 2f86834, republished under its MIT licence (© commitizen-tools). 378 words, ~839 tokens.
Download SKILL.mdSave it as
.claude/skills/commitizen/SKILL.md (or your agent's skills folder).- name
- commitizen
- description
- Use this skill for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the Commitizen CLI.
- license
- MIT
- metadata.project
- commitizen-tools/commitizen
- metadata.docs
- https://commitizen-tools.github.io/commitizen/
- metadata.install
- pipx install commitizen
Commitizen
Commitizen is a CLI for enforcing Conventional Commits, automating version bumps, and generating changelogs.
Use this skill when
- A task involves commit message authoring or validation.
- A repository needs Commitizen initialization or configuration updates.
- Work depends on version schemes, version providers, version files, tags, or changelog behavior.
- CI/CD automation needs commit validation, automated version bumps, or release notes.
Core workflow
- Find the active configuration file in this order:
.cz.toml,cz.toml,.cz.json,cz.json,.cz.yaml,cz.yaml, thenpyproject.tomlunder[tool.commitizen]. - Read the effective settings before acting, especially
name,version,version_provider,version_scheme,version_files,tag_format,update_changelog_on_bump,annotated_tag,bump_message,pre_bump_hooks, andpost_bump_hooks. - Match the command to the task:
cz commitfor interactive commit authoringcz checkfor validating commit messages or git rangescz initfor bootstrapping configurationcz bumpfor calculating or applying release versionscz changelogfor generating or updatingCHANGELOG.mdcz lsfor listing available commit rulescz versionfor showing the current version
- Prefer read-only inspection first. Safe discovery commands include
cz version,cz ls,cz check,cz bump --get-next, andcz bump --dry-run. - Treat
cz bumpas stateful: it can update version files, create a bump commit, and create a git tag. Verify the version provider, version scheme, tag format, and changelog settings before running it for real. - When automating in CI, check whether the workflow should ignore specific exit codes with
--no-raiseand whetherbump_messageshould include skip-CI text. - After making changes, validate the resulting configuration, commands, and automation against the repository's actual version scheme and provider.
Show full SKILL.md (122 more words)Show less
Important domain details
- Commitizen supports both global installation (recommended for the
czCLI) and project-local installation; see the installation section indocs/README.mdfor the full matrix of supported tools. - The default version scheme is PEP 440;
semverandsemver2are also supported. - Common version providers include
commitizen,pep621,poetry,cargo,npm,composer,uv, andscm. cz changeloggenerates Markdown changelogs.cz commitsupports--dry-runand--write-message-to-file.cz checkcan validate a literal message, a commit-msg file, or a git revision range.
Examples
- Validate one message:
cz check --message "feat(cli): add release command" - Validate branch history:
cz check --rev-range master..HEAD - Preview the next version:
cz bump --get-next - Preview bump details:
cz bump --dry-run - Preview changelog output:
cz changelog --dry-run - Initialize configuration:
cz init
© commitizen-tools, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/commitizen of commitizen-tools/commitizen.
Open the folder on GitHubat commit 2f86834
Compare with similar skills
Commitizen next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Commitizen this skillcommitizen-tools/commitizen | 3.5k | — | ~839 | Automated safety check: Pass | MIT | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Saleor Commit Workflowsaleor/saleor | 23k | — | ~575 | Automated safety check: Pass | BSD-3-Clause | |
| pybind11 Release Preparationpybind/pybind11 | 18k | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
pybind11 Release Preparation
pybind/pybind11
Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.
pybind11 Release Publication
pybind/pybind11
Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.
Related
Categories
Questions about Commitizen
What does Commitizen do?
A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…. Commitizen is an agent skill from commitizen-tools/commitizen. Use this skill for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the Commitizen CLI.
When should I use Commitizen?
Commitizen fits situations like: tasks involving Conventional Commits; commit message validation; commitizen configuration; semantic version bumps.
How do I install Commitizen in Claude Code?
Run `npx skills add commitizen-tools/commitizen --skill commitizen -a claude-code`. Or copy the skill folder (.agents/skills/commitizen in commitizen-tools/commitizen) into .claude/skills/commitizen in your project. Claude Code loads it when a task matches its description.
How do I install Commitizen in Codex?
Run `npx skills add commitizen-tools/commitizen --skill commitizen -a codex`. Or copy the skill folder (.agents/skills/commitizen in commitizen-tools/commitizen) into .agents/skills/commitizen in your project. Codex loads it when a task matches its description.
Can I use Commitizen in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add commitizen-tools/commitizen --skill commitizen -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commitizen, .gemini/skills/commitizen, .github/skills/commitizen and .opencode/skills/commitizen in your project.
What does Commitizen need to run?
SKILL.md names no scripts, command-line tools or credentials: Commitizen is instructions for the agent only.
Does Commitizen access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Commitizen safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Commitizen use?
Commitizen is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Commitizen use?
About 839 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Commitizen?
Skills that share tags, products or a category with Commitizen: React Router Release Notes Prep (remix-run/react-router, 57k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Saleor Commit Workflow (saleor/saleor, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Commitizen?
commitizen-tools (a GitHub organization) maintains it in commitizen-tools/commitizen, which has 3,526 GitHub stars. The repository was last updated on October 7, 2026.
Source: commitizen-tools/commitizen on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.