Commitlint
commitlint.js.org › reference › rules.html
Rules | commitlint
commitlint · SearchK · Appearance · Menu · Return to top · condition: body is in case value · rule: always · value · text · 'lower-case' possible values ·
GitHub
github.com › conventional-changelog › commitlint
GitHub - conventional-changelog/commitlint: 📓 Lint commit messages
Node v24 changes the way that modules are loaded, and this includes the commitlint config file. If your project does not contain a package.json, commitlint may fail to load the config, resulting in a Please add rules to your commitlint.config.js error message.
Starred by 18.5K users
Forked by 965 users
Languages TypeScript 92.2% | JavaScript 7.8%
npm
npmjs.com › package › @commitlint › rules
commitlint/rules
May 8, 2025 - Lint your commit messages. Latest version: 19.8.1, last published: 4 months ago. Start using @commitlint/rules in your project by running `npm i @commitlint/rules`. There are 11 other projects in the npm registry using @commitlint/rules.
» npm install @commitlint/rules
Commitlint
commitlint.js.org › reference › configuration.html
Configuration | commitlint
* Referenced package must be installed */ formatter: "@commitlint/format", /* * Any rules defined here will override rules from @commitlint/config-conventional */ rules: { "type-enum": [2, "always", ["foo"]], }, /* * Array of functions that return true if commitlint should ignore the given message.
Commitlint
commitlint.js.org › reference › rules-configuration.html
Rules configuration | commitlint
Rules are made up by a name and a configuration array. The configuration array contains: · Rule configurations are either of type array residing on a key with the rule's name as key on the rules object or of type function returning type array or Promise<array>. This means all of the following ...
Commitlint
commitlint.js.org
commitlint
To get the most out of commitlint you'll want to automate it in your project lifecycle.
Conventional Commits
conventionalcommits.org › en › v1.0.0
Conventional Commits
types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.
GitHub
github.com › conventionalcommit › commitlint
GitHub - conventionalcommit/commitlint: commitlint checks if your commit messages meets the conventional commit format · GitHub
February 22, 2026 - To validate a config file, run commitlint config check /path/to/conf.yaml · To lint a message, you can use any one of the following ... min-version: v0.11.0 formatter: default rules: - header-min-length - header-max-length - body-max-line-length - footer-max-line-length - type-enum severity: default: error rules: {} settings: body-max-line-length: argument: 100 flags: {} footer-max-line-length: argument: 100 flags: {} header-max-length: argument: 72 flags: {} header-min-length: argument: 10 flags: {} type-enum: argument: - feat - fix - docs - style - refactor - perf - test - build - ci - chore - revert flags: {} disable-default-ignores: false ignores: []
Starred by 86 users
Forked by 9 users
Languages Go 91.4% | Shell 8.6%
npm
npmjs.com › package › @commitlint › config-conventional
commitlint/config-conventional
March 15, 2026 - echo "fix: some message body with multiple lines has a message that is way too long and will break the line rule 'line-max-length' by several characters" # fails echo "fix: some message body with multiple lines but still no line is too long" # passes · conventional-changelog · commitlint ·
» npm install @commitlint/config-conventional
Published Mar 15, 2026
Version 20.5.0
Top answer 1 of 2
10
I had the same issue and was able to overcome it by adding this section to my package.json, which configures commitlint to use config-conventional.
"commitlint": {
"extends": [
"@commitlint/config-conventional"
]
},
Also ensure that you installed both dev dependencies.
"@commitlint/cli": "18.0.0",
"@commitlint/config-conventional": "18.0.0",
You can find this also in the commitlint projects package.json. ;- )
https://github.com/conventional-changelog/commitlint/blob/master/package.json
2 of 2
0
This is my dependency package
"devDependencies": {
"@commitlint/cli": "^19.7.1",
"@commitlint/config-conventional": "^19.7.1",
"@types/node": "18.18.13",
"commitizen": "^4.3.1",
"cz-conventional-changelog": "^3.3.0",
"husky": "^9.1.7"
}
You can try changing the file name of commitilint.config. js to commitilint.config. cjs
// commitlint.config.cjs
module.exports = {
extends: ['@commitlint/config-conventional']
}
Please also note that the file encoding is utf-8
Commitlint
commitlint.js.org › reference › examples.html
Examples | commitlint
{ // ... "commitlint": { "rules": { "references-empty": [2, "never"], }, "parserPreset": { "parserOpts": { "issuePrefixes": ["PROJ-"], }, }, }, // ...
GitHub
github.com › conventional-changelog › commitlint › blob › master › docs › reference › rules.md
commitlint/docs/reference/rules.md at master · conventional-changelog/commitlint
This rule enforces that breaking changes are marked by both a ! in the header and BREAKING CHANGE in the footer.
Author conventional-changelog
Medium
arunkumarvallal.medium.com › become-a-pro-at-commit-messages-using-commitlint-56dab86333b3
Become a Pro at Commit Messages using Commitlint | by Arun kumar V | Medium
October 23, 2023 - Commitlint maintains consistent formatting and style for commit messages in version control systems like Git. It helps ensure that developers follow a specific set of rules or conventions when writing commit messages, making it easier to manage and maintain a project’s commit history and ...
npm
npmjs.com › package › commitlint-plugin-function-rules
commitlint-plugin-function-rules - npm
May 29, 2025 - commitlint plugin to use functions as rule value. Latest version: 4.3.0, last published: 7 days ago. Start using commitlint-plugin-function-rules in your project by running `npm i commitlint-plugin-function-rules`. There are 20 other projects in the npm registry using commitlint-plugin-fun...
» npm install commitlint-plugin-function-rules
Published Jan 06, 2026
Version 4.3.0
Author Jeroen de Bruijn
GitHub
github.com › conventional-changelog › commitlint › tree › master › @commitlint › config-conventional
commitlint/@commitlint/config-conventional at master · conventional-changelog/commitlint
npm install --save-dev @commitlint/config-conventional @commitlint/cli echo "export default {extends: ['@commitlint/config-conventional']};" > commitlint.config.js · The following rules are considered problems for @commitlint/config-conventional and will yield a non-zero exit code when not met.
Author conventional-changelog
Npm
npm.io › package › @commitlint › rules
@commitlint/rules NPM | npm.io
Adoption: Make ahmed-taj/commitlint-bot configurable via commitlint configuration ... DX: Extend the configuration schema to allow for additional fields (descriptions, examples, fixes) on both the rule and value level