chinese-commit-conventions

Standardize Chinese commit messages and automate changelog workflows.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/zhuyingcoder/cc-demo --skill chinese-commit-conventions-zhuyingcoder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chinese-commit-conventions
Source: https://github.com/zhuyingcoder/cc-demo/tree/main/.claude/skills/chinese-commit-conventions
Command: npx skills add https://github.com/zhuyingcoder/cc-demo --skill chinese-commit-conventions-zhuyingcoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chinese teams often struggle with inconsistent commit messages and manual changelog maintenance. This skill provides a standardized approach to commit types, scopes, and message bodies, enabling automatic changelog generation and better history readability.

Core Features & Use Cases

  • Conventional Commits 中文适配: Aligns commit type taxonomy with Chinese workflows, enabling clear history and automated parsing.
  • Templates & Rules: Subject, body, and footer templates enforce concise, actionable messages and issue linking.
  • Changelog Automation: Integrates with conventional changelog tooling to produce consistent release notes.

Quick Start

使用本技能的模板和钩子在你的项目中启用提交规范,并开始按照 <type>(<scope>): <subject> 的格式提交。

Frequently Asked Questions about chinese-commit-conventions

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

FAQPage Schema
How do I automate changelog generation for Chinese teams using conventional commits?

You can automate changelog generation for Chinese teams by applying Conventional Commits adaptations and integrating conventional changelog tooling to parse standardized commit messages into consistent release notes.

What is the standard git commit message format for linking issues in a Chinese workflow?

The standard git commit message format for linking issues follows the <type>(<scope>): <subject> structure, utilizing specific subject, body, and footer templates to enforce concise, actionable messages and issue linking.

How do I configure commitlint and Husky to enforce git commit conventions?

To configure commitlint and Husky for enforcing git commit conventions, you use editor hooks and YAML frontmatter-based identification to integrate rules that validate commit messages against your defined templates.

Does conventional commits support Chinese adaptations for commit type taxonomy?

Yes, conventional commits supports Chinese adaptations by aligning the commit type taxonomy with Chinese workflows, which enables clear git history readability and automated parsing for native teams.

Can I extend commit message templates with custom scripts and references?

You can extend commit message templates with optional scripts, references, and assets to expand functionality across your documentation, CI pipelines, and editor hooks within your development workflow.

Why do I need YAML frontmatter identification for commit message linting?

YAML frontmatter identification is required for commit message linting to enforce standardized identification, ensuring that commit types, scopes, and message bodies align with the configured conventional commits rules.