chinese-commit-conventions

Keep the type keyword in English (feat, fix, docs, etc.) for toolchain compatibility, and write the scope and description in Chinese. Use verb-object phrases like "添加 xxx" or "修复 xxx", keep the subject under 50 characters, and omit the trailing period.

Install @commitlint/cli and @commitlint/config-conventional, then extend the conventional config in commitlint.config.js. Disable subject-case, raise header-max-length to around 120, and define the allowed type-enum list to accommodate Chinese characters.

Use conventional-changelog-cli or standard-version with a .versionrc.js file that maps commit types to Chinese section names like 新功能, 缺陷修复, and 性能优化. Run the changelog npm script to update CHANGELOG.md from commit history.

Yes, husky's commit-msg hook can invoke commitlint to validate every commit message before it is accepted. Add "npx --no -- commitlint --edit $1" to .husky/commit-msg so non-compliant messages are rejected automatically.

Mark it whenever the commit introduces incompatible changes such as database schema modifications, public API parameter or response changes, or config format changes. Add a BREAKING CHANGE footer describing the migration steps, or append an exclamation mark after the type.

Default rules like subject-case and header-max-length are tuned for English and often reject Chinese text. Disable subject-case and increase header-max-length and body-max-line-length limits in your commitlint configuration.