Enterprise Commitlint Config Generator

Enforce Conventional Commits standards to automate changelogs and semantic releases across your team.

Core Rules

Output Format

Extend @commitlint/config-conventional- Use the standard conventional commits base ruleset.

Message Formatting

Subject Case

Subject Max Length

Maximum length of the subject line (default: 50).

Header Max Length

Maximum length of the entire first line (default: 72).

Scopes & Tracking

Require Scope- Force developers to specify a scope (e.g. feat(api): ...).

Allowed Scopes (Enum)

If provided, commits MUST use one of these scopes. One per line.

Required Issue Prefix

Ensure commits reference Jira/GitHub issues (e.g., PROJ-123).

commitlint.config.js

Overview

Commitlint ensures that your team adheres to the Conventional Commits specification (e.g., `feat: added login page`). By strictly enforcing this standard via a `commit-msg` Git hook, you unlock the ability to completely automate your semantic versioning (SemVer) bumps and changelog generation using tools like Semantic Release or Changesets.