ref-sp-py-commitizenlisted

# Python Commitizen ## Purpose Guide agents through using the Python `commitizen` package as the owner for conventional commits, semantic version bumps, changelog generation, release tags, and version-file updates. ## When to use this skill - Adding or reviewing `[tool.commitizen]` in `pyproject.toml`. - Choosing a Commitizen `version_provider` for a Python, uv, mixed Python/Node, or tag-derived release workflow. - Designing `cz bump`, `cz changelog`, `cz check`, or project wrapper commands. - Debugging version drift, missing release tags, changelog ranges, or conventional-commit parsing. - Deciding whether Commitizen should replace custom version or changelog scripts. - Deciding whether a mixed Python/Node repo should keep Commitizen or move to an explicit release-intent workflow such as Changesets. ## Scope Boundaries - Use `ref-sp-dev-package-management` for general package metadata, changelog ownership, and multi-manifest release policy. - Use `ref-sp-dev-semantic-versioning` for bump meaning, prerelease stability, and dependency-range decisions. - Use `ref-sp-dev-git-commits` for commit grouping, commit bodies, and day-to-day commit message quality. - Use this skill for Commitizen-specific commands, configuration, and failure modes. ## Default Position Prefer Commitizen when a repo already wants conventional commits and generated changelogs. Let it own the normal release-prep step instead of maintaining separate custom version writers, unless the repo needs behav