REGEXVAULTv2.0
Dev & Systems/Git
Verified Safe

Conventional Commit Message Regex for PHP

/^(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 PHP. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your PHP project — whether you're validating in a Laravel validator, a WordPress plugin, or a standalone PHP script.

Php Implementation

Php
<?php
// Conventional Commit Message
// ReDoS-safe | RegexVault — Dev & Systems > Git

define('CONVENTIONAL_COMMIT_MESSAGE_PATTERN', '/^(feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert|wip)(?:\(([a-zA-Z0-9\-_\/]+)\))?(!)?: (.+)$/');

function validate_conventional_commit_message(string $input): bool {
    return (bool) preg_match(CONVENTIONAL_COMMIT_MESSAGE_PATTERN, $input);
}

// Example
var_dump(validate_conventional_commit_message("feat: add user authentication")); // bool(true)

Test Cases

Matches (Valid)
Rejects (Invalid)
feat: add user authenticationadd feature
fix(auth): resolve token expiry bugFIX: resolve bug
feat(api)!: remove deprecated endpointfeat(): empty scope
docs: update READMEfeat:
chore(deps): bump lodash to 4.17.21unknown: 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 PHP developers because especially relevant in PHP where PCRE backtracking limits can trigger silent failures on malicious input. 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