Conventional Commit Message Regex for Python
/^(feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert|wip)(?:\(([a-zA-Z0-9\-_/]+)\))?(!)?: (.+)$/What this pattern does
This page provides a comprehensive, battle-tested regular expression for matching conventional commit message, ported and verified for Python. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Python project — whether you're validating in a Django view, a FastAPI endpoint, or a standalone data processing script.
Python Implementation
# Conventional Commit Message
# ReDoS-safe | RegexVault — Dev & Systems > Git
import re
conventional_commit_message_pattern = re.compile(r'^(feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert|wip)(?:\(([a-zA-Z0-9\-_/]+)\))?(!)?: (.+)$')
def validate_conventional_commit_message(value: str) -> bool:
return bool(conventional_commit_message_pattern.fullmatch(value))
# Example
print(validate_conventional_commit_message("feat: add user authentication")) # TrueTest Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
feat: add user authentication | add feature |
fix(auth): resolve token expiry bug | FIX: resolve bug |
feat(api)!: remove deprecated endpoint | feat(): empty scope |
docs: update README | feat: |
chore(deps): bump lodash to 4.17.21 | unknown: message type |
When to use this pattern
This pattern is drawn from the Dev & Systems > Git category and carries a ReDoS-safe certification. That matters for Python developers because particularly important in Python web servers where CPU-bound regex operations can stall concurrent request handling. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.
Common Pitfalls
The ! indicator is separate from 'BREAKING CHANGE:' in the footer — both must be detected. A commit with feat!: triggers a major version bump in semantic-release tooling.
Technical Notes
Group 1 = type, group 2 = scope (optional), group 3 = ! breaking change (optional), group 4 = description. BREAKING CHANGE can also appear in the footer. Conventional commits enable automated changelog generation.
Have a pattern that belongs in the vault?
Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.
Submit a Pattern