chinese-commit-conventions

Name: chinese-commit-conventions
Availability: InStock
Author: dascard

Standardize Git commit messages with Conventional Commits for Chinese teams.

2|Updated Apr 6, 2026

Search Tags:#automation #git #workflow #changelog #commit #conventional-commits

Ready to run

npx skills add https://github.com/dascard/nanobot --skill chinese-commit-conventions-dascard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chinese-commit-conventions
Source: https://github.com/dascard/nanobot/tree/main/.agents/skills/chinese-commit-conventions
Command: npx skills add https://github.com/dascard/nanobot --skill chinese-commit-conventions-dascard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @commitlint/cli, @commitlint/config-conventional, husky, lint-staged, conventional-changelog-cli.

What problem does it solve?

This Skill addresses the lack of consistency in Git commit messages within Chinese-speaking development teams, ensuring that project history remains readable, searchable, and compatible with automated changelog generation tools.

Core Features & Use Cases

Conventional Commits Adaptation: Provides a clear mapping of standard types (feat, fix, etc.) to Chinese team workflows.
Automated Tooling: Includes configurations for commitlint, husky, and lint-staged to enforce standards at the pre-commit level.
Use Case: A team struggling with vague commit messages like "fixed bug" can use this Skill to enforce a structured format that includes the scope, description, and detailed body, enabling automated generation of professional CHANGELOG.md files.

Quick Start

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

To enforce conventional commits for a Chinese development team, configure commitlint and husky pre-commit hooks to validate structured Git commit message formats including type, scope, and description.

How do I automate changelog generation from Git commit messages?▼

Automate changelog generation by standardizing Git commit messages with the Conventional Commits specification, enabling conventional-changelog-cli to parse structured history and automatically generate a professional CHANGELOG.md file.

Does husky and lint-staged work with commitlint to validate commit messages?▼

Yes, husky and lint-staged integrate with commitlint to intercept Git commits at the pre-commit level, ensuring that commit messages adhere to configured Conventional Commits standards before they are saved.

What is the best way to structure Git commit messages for automated release notes?▼

The best way to structure Git commit messages for automated release notes is using the Conventional Commits format, mapping standard types like feat and fix to your workflow to maintain consistent version control history.

Why should I use conventional commits instead of free-text Git messages?▼

Conventional commits replace vague free-text Git messages with a structured format that improves code review clarity, maintains readable project history, and satisfies requirements for automated release note maintenance.

Can I customize the conventional commits config for specific project workflows?▼

You can customize the conventional commits configuration by adapting standard types to match Chinese team workflows, defining specific scopes and descriptions within commitlint to fit your project's version control requirements.