chinese-commit-conventions

Configures commitlint, husky, and lint-staged for Chinese-localized Conventional Commits.

21|9|Updated May 27, 2026
One-click install
npx skills add https://github.com/cq112233/unibestX --skill chinese-commit-conventions-cq112233
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chinese-commit-conventions
Source: https://github.com/cq112233/unibestX/tree/main/.agents/skills/chinese-commit-conventions
Command: npx skills add https://github.com/cq112233/unibestX --skill chinese-commit-conventions-cq112233

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of consistency in team Git commit messages by providing a structured, Chinese-localized implementation of the Conventional Commits specification, ensuring that commit history is readable, searchable, and compatible with automated changelog generation.

Core Features & Use Cases

  • Standardized Templates: Provides clear type definitions and message formats tailored for Chinese development teams.
  • Tooling Integration: Includes configurations for commitlint, husky, and lint-staged to enforce commit quality automatically.
  • Use Case: A development team wants to automate their release notes and ensure all developers follow the same format for features, fixes, and refactors; this skill provides the exact configuration files and guidelines to implement this workflow immediately.

Quick Start

Use the chinese-commit-conventions skill to initialize the commitlint and husky configuration in the current 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 configure commitlint and husky to enforce conventional commits in a Chinese development team?

To enforce conventional commits in a Chinese environment, configure commitlint and husky by integrating standardized templates and lint-staged. This setup automatically validates Git commit messages, ensuring structured and readable project history for the entire team.

What is the best way to generate a Chinese-friendly changelog from Git commit history?

Generating a Chinese-friendly changelog involves applying the Conventional Commits specification adapted for Chinese language environments. By standardizing commit message formats first, teams can automate release documentation and maintain consistent project history.

Does conventional commits work with husky and lint-staged for automated versioning workflows?

Yes, conventional commits works with husky and lint-staged for automated versioning workflows. Integrating these tools enforces commit message quality automatically, satisfying requirements for consistent project history and automated release documentation generation.

How do I standardize Git commit messages for features, fixes, and refactors?

Standardizing Git commit messages requires defining clear type definitions and message formats for features, fixes, and refactors. Using commitlint configurations enforces these structured templates, improving team collaboration through consistent commit metadata.

When do I need to use a localized conventional commits specification for my Git history?

You need a localized conventional commits specification when your development team requires readable, searchable Git history in Chinese. It solves the lack of consistency in team commit messages by providing structured templates tailored for Chinese language environments.