chinese-commit-conventions

Configures Chinese-language Conventional Commits, commitlint, husky, and changelog tooling for Git workflows.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/bill80362/laravel-thread-admin --skill chinese-commit-conventions-bill80362
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chinese-commit-conventions
Source: https://github.com/bill80362/laravel-thread-admin/tree/main/.github/superpowers/chinese-commit-conventions
Command: npx skills add https://github.com/bill80362/laravel-thread-admin --skill chinese-commit-conventions-bill80362

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams writing Git commit messages in Chinese lack a standardized convention and tooling setup, leading to inconsistent commit history, broken changelog generation, and unenforceable review standards. ## Core Features & Use Cases - Chinese Conventional Commits Spec: Adapts Conventional Commits 1.0.0 with English type keywords (feat, fix, docs, etc.) and Chinese scope/subject/body, including subject rules, body templates, and BREAKING CHANGE annotation conventions. - Toolchain Configuration: Provides ready-to-use configs for commitlint (Chinese-friendly rules), husky hooks, lint-staged, commitizen interactive prompts, and conventional-changelog/standard-version with Chinese section titles. - Issue Linking & Team Rollout: Covers GitHub/Gitee/Coding issue reference formats and a team adoption checklist with self-review items. - Use Case: A Chinese development team wants to enforce commit standards and auto-generate a Chinese CHANGELOG; apply this Skill to configure commitlint.config.js, husky hooks, and .versionrc.js in one pass. ## Quick Start Ask the assistant to set up Chinese Conventional Commits with commitlint, husky, and Chinese changelog generation for your repository.

Frequently Asked Questions about chinese-commit-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write Chinese commit messages following Conventional Commits?

Keep the type keyword in English (feat, fix, docs, etc.) and write the scope and description in Chinese, using a verb-object phrase under 50 characters without a trailing period. Add a Chinese body explaining motivation, approach, and impact scope.

How to configure commitlint to allow Chinese characters in commit messages?

Extend @commitlint/config-conventional, disable the subject-case rule, and raise header-max-length to around 120 since Chinese characters are wider. Keep type-enum restricted to the standard types like feat, fix, and chore.

How do I generate a Chinese CHANGELOG from conventional commits?

Install conventional-changelog-cli and configure .versionrc.js with a types array mapping each commit type to a Chinese section title like 新功能 or 缺陷修复. Run the changelog script to regenerate CHANGELOG.md from commit history.

Does husky work with commitlint for enforcing commit message rules?

Yes, husky's commit-msg hook can run commitlint --edit on every commit, rejecting messages that violate the configured rules. Combine it with a pre-commit hook running lint-staged for code formatting checks.

When should a commit be marked as BREAKING CHANGE?

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