conventional-pre-commit
A pre-commit hook that checks commit messages for Conventional Commits formatting.
Decision gist · record as of 2026-08-14
Yes. This is a low-friction, actively maintained tool that solves a real problem—enforcing commit message consistency—with no dependencies and permissive licensing. It's well-suited for teams adopting Conventional Commits. Install it if your project needs standardized commit messages for changelog automation or team discipline; skip it if you have no such requirement.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires pre-commit framework to be installed and initialized in your repository; works with Python >= 3.8.
- Low friction install with no runtime dependencies.
- Active maintenance with recent releases; last commit 2026-07-20 and latest release 2026-02-18 indicate ongoing support.
License · maintenance · safety
permissive license (permissive) — Apache 2.0 permissive license allows free use, modification, and distribution with minimal restrictions—suitable for both open-source and commercial projects.
last release 2026-02-18 (177 days) · last repo commit 2026-07-20 · 548 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 135,238 downloads/mo, #11,446 on PyPI
Alternatives
Verify before relying
pip install conventional-pre-commit
Add to .pre-commit-config.yaml:
repos:
- repo: https://github.com/compilerla/conventional-pre-commit
rev: v4.4.0
hooks:
- id: conventional-pre-commit
stages: [commit-msg]
Then: pre-commit install --install-hooks
Or use directly in Python:
from conventional_pre_commit.format import is_conventional
print(is_conventional("feat: add new feature"))- Whether custom type validation and scope enforcement work reliably across all git workflows and edge cases.
- Performance impact when used in repositories with large commit histories or frequent commits.
What it is and what it does
conventional-pre-commit is a pre-commit hook that enforces Conventional Commits formatting on git commit messages. It integrates with the pre-commit framework to block commits that don't follow the pattern type(scope): subject, rejecting messages like "add a new feature" while accepting "feat: add a new feature". The hook supports customization through arguments to restrict allowed commit types (feat, fix, chore, etc.), enforce scope presence, define allowed scopes, and enable strict mode to disallow fixup and merge commits.
It can be deployed as a pre-commit hook in your repository's workflow or installed standalone via pip for command-line or programmatic use. The package has no runtime dependencies and integrates cleanly into existing development workflows. It provides clear error messages showing what went wrong and how to fix the commit message, with optional verbose output explaining the expected format.
Use it for
- Enforce Conventional Commits across a team to enable automated changelog generation and semantic versioning.
- Validate commit message format in CI/CD pipelines by running the command-line tool on commit message files.
- Restrict commits to a specific set of types (e.g., feat, fix, docs) and require scope specification for better commit organization.
- Prevent non-compliant commits from entering the repository during local development via pre-commit hook integration.
- Use the Python API to validate commit messages programmatically in custom tooling or scripts.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
This is a low-friction, actively maintained tool that solves a real problem—enforcing commit message consistency—with no dependencies and permissive licensing. It's well-suited for teams adopting Conventional Commits. Install it if your project needs standardized commit messages for changelog automation or team discipline; skip it if you have no such requirement.
Install
conventional-pre-commit on PyPI
Before you install
Low friction install with no runtime dependencies. Active maintenance with recent releases; last commit 2026-07-20 and latest release 2026-02-18 indicate ongoing support.
Requires pre-commit framework to be installed and initialized in your repository; works with Python >= 3.8.
License in practice
Apache 2.0 permissive license allows free use, modification, and distribution with minimal restrictions—suitable for both open-source and commercial projects.
Quickstart
pip install conventional-pre-commit
Add to .pre-commit-config.yaml:
repos:
- repo: https://github.com/compilerla/conventional-pre-commit
rev: v4.4.0
hooks:
- id: conventional-pre-commit
stages: [commit-msg]
Then: pre-commit install --install-hooks
Or use directly in Python:
from conventional_pre_commit.format import is_conventional
print(is_conventional("feat: add new feature"))Verify before relying
- Whether custom type validation and scope enforcement work reliably across all git workflows and edge cases.
- Performance impact when used in repositories with large commit histories or frequent commits.
Package facts
| License | permissive license permissive |
| Python support | Supports the current Python release >=3.8 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | None |
| Maintenance | Actively maintained 177 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 135,238 / month, #11,446 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Programming Language :: Python :: 3 :: Only |
Evidence: conventional_pre_commit-4.4.0-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “conventional commits validation”
- conventional-pre-commitA pre-commit hook that validates git commit messages against…
- commitlintLints commit messages against the Conventional Commits standard,…
- commit-checkValidates Git commit messages, branch names, author identity, and…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also commit-check · commitlint · commitizen · git-cliff · check-jsonschema · pre-commit-hooks · pre-commit-uv · release-tag · add-trailing-comma