# commitizen/cz-cli

The commitizen command line utility. #BlackLivesMatter

Repository: https://github.com/commitizen/cz-cli
Canonical: https://ross.abutalabs.com/products/cz-cli
Homepage: http://commitizen.github.io/cz-cli/
Language: JavaScript
License: MIT
License Family: permissive
Topics: commitizen, javascript, commit-hooks, node, semantic-versioning, semantic-release, command-line, utilities, commitizen-adapter, git
Last push: 2026-08-11T23:42:06+00:00

## Health v2 (maintenance only)
Score: 83/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 97, release rhythm 56, longevity 100
- inputs: {"age_days": 4154, "days_push": 22, "days_rel": 82, "gap_med": 623, "n_releases_24m": 2}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 17498, forks 564 (observed 2026-08-28T04:11:19.932630+00:00)

## What it is
Commitizen is a Node.js command-line tool that replaces `git commit` with an interactive prompt (`git cz` or `cz`) that guides contributors through filling in required commit message fields. It enforces project-defined commit conventions via pluggable adapters, giving instant feedback instead of relying on post-hoc commit hooks to reject bad messages.

## Use cases
- enforce conventional commit message formats across a team
- prompt contributors for required commit fields instead of reading CONTRIBUTING.md
- avoid commit hook rejections by validating format at commit time
- standardize commit messages for semantic-release and changelog generation
- run interactive commits via npx cz or an npm script

## When to choose
- your project follows (or wants) a structured commit convention like Conventional Commits
- you use semantic-release or automated changelogs that depend on consistent commit messages
- you want contributor-friendly, guided commit formatting with adapter customization

## When to avoid
- your team has no commit message conventions or doesn't want them enforced
- you prefer lightweight git hooks validating messages after the fact
- your workflow doesn't use Node.js/npm tooling

## Facets
- artifact type: cli-tool
- maturity: stable
- function: cli, developer-tools, version-control
- domain: developer-tools, version-control
- platform: cli, cross-platform
- tags: commit-conventions, conventional-commits, git, semantic-versioning, interactive-prompt, commitizen-adapters, command-line, nodejs

## Member repositories
- commitizen/cz-cli (main) score 83

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:11:19.932630+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:02:54.985689+00:00, confidence not recorded.
  - readme: https://github.com/commitizen/cz-cli (fetched 2026-08-28T04:11:19.932630+00:00, sha 90707f88193d)
  - homepage: http://commitizen.github.io/cz-cli/ (fetched 2026-08-29T08:01:16.405015+00:00, sha 835931f081a0)
- Data as of 2026-08-30T08:39:29.467469+00:00.