Agent skill

Chinese Commit Conventions

by jnMetaCode in jnMetaCode/superpowers-zh

Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms.

MITAuto-check passedDevelopment

SKILL.md written in Chinese; this summary is our English description.

Install Chinese Commit Conventions

skills CLI
$ npx skills add jnMetaCode/superpowers-zh --skill chinese-commit-conventions -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jnMetaCode/superpowers-zh chinese-commit-conventions --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/chinese-commit-conventions .claude/skills/chinese-commit-conventions && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
chinese-commit-conventions
GitHub stars
8.3k
Used in
1 other repo
Token cost
~1.6k tokens
SKILL.md length
242 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms.

  • Works in 10 steps: Conventional Commits 中文适配 → 中文 commit message 模板 → Subject 行规范 → …
  • Writing git commit messages in Chinese with a consistent structure
  • SKILL.md covers 1. Conventional Commits 中文适配, 2. 中文 commit message 模板, 3. Subject 行规范 and 4. Body 编写规范, plus 4 more sections
  • Calls npm and npx; reaches gitee.com

What it does

The skill adapts Conventional Commits 1.0.0 for Chinese-speaking teams. Ten types are defined with example scenarios: feat, fix, docs, style, refactor, perf, test, chore, ci and revert. Type keywords stay in English for toolchain compatibility, while scope, description and body are written in Chinese. Subjects use verb-object phrases without a trailing period, stay within 50 characters and avoid empty descriptions such as changed the code.

Bodies explain why, how and what is affected, with lines kept to 72 characters and a blank line after the title. Breaking changes go in a footer or with an exclamation mark after the type, and the team convention requires them for database schema, public API and config format changes, together with migration steps. Issue links are shown for GitHub, Gitee and Coding. The description also lists commitlint, husky, commitizen and conventional-changelog templates in Chinese, and says to run the skill only when you call /chinese-commit-conventions explicitly.

When your agent uses it

  • Writing git commit messages in Chinese with a consistent structure
  • Setting up commitlint, husky or commitizen for a Chinese-speaking team
  • Linking commits to GitHub, Gitee or Coding issues
  • Marking breaking changes together with migration steps

Example prompts

  • “/chinese-commit-conventions 帮我为这次修复订单超卖的改动写一条提交信息。”
  • “Set up commitlint and commitizen with the Chinese Conventional Commits rules for this repo.”
  • “Write a breaking-change footer for the new nested user info response, including how to migrate.”

Requirements

  • Node.js tooling, if you adopt commitlint, husky or commitizen

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Conventional Commits 中文适配
  2. 中文 commit message 模板
  3. Subject 行规范
  4. Body 编写规范
  5. Breaking Changes 标注
  6. Issue 关联
  7. Changelog 自动生成配置
  8. commitlint 中文配置
  9. husky + lint-staged 集成
  10. 团队规范检查清单

What it can do on your machine

Read from SKILL.md and the folder at commit fe34019. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • gitee.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Chinese Commit Conventions loads about 1.6k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 242 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jnMetaCode/superpowers-zh at commit fe34019, republished under its MIT licence (© jnMetaCode). 242 words, ~1,648 tokens.

Download SKILL.mdSave it as .claude/skills/chinese-commit-conventions/SKILL.md (or your agent's skills folder).
name
chinese-commit-conventions
description
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用,不要根据上下文自动触发。
version
1.0.0
license
MIT

中文 Git 提交规范

1. Conventional Commits 中文适配

基于 Conventional Commits 1.0.0 规范,针对中文团队的实际使用习惯进行适配。

类型(type)定义
类型说明示例场景
feat新功能添加用户注册模块
fix修复缺陷修复登录页白屏问题
docs文档变更更新 API 接口文档
style代码格式(不影响逻辑)调整缩进、补充分号
refactor重构(非新功能、非修复)拆分过长的服务类
perf性能优化优化首页列表查询速度
test测试相关补充用户模块单元测试
chore构建/工具/依赖变更升级 webpack 到 v5
ci持续集成配置修改 GitHub Actions 流程
revert回滚提交回滚 v2.1.0 的登录重构
原则
  • type 保留英文关键字(工具链兼容性好)
  • scope 和 description 使用中文
  • body 使用中文完整描述

2. 中文 commit message 模板

<type>(<scope>): <subject>

<body>

<footer>
完整示例
feat(用户模块): 添加手机号一键登录功能

- 接入运营商一键登录 SDK
- 支持移动、联通、电信三网
- 登录失败自动降级到短信验证码

Closes #128
fix(订单): 修复并发下单导致库存超卖的问题

在高并发场景下,原有的库存扣减逻辑存在竞态条件。
改用 Redis 分布式锁 + 数据库乐观锁双重保障。

影响范围:订单服务、库存服务
测试确认:已通过 500 并发压测验证

Closes #256

3. Subject 行规范

格式
<type>(<scope>): <description>
规则
  • type: 必填,从上方类型表中选取
  • scope: 选填,表示影响范围,使用中文模块名
    • 示例:用户模块、订单、支付、基础组件
  • description: 必填,中文简述,不超过 50 个字符
    • 使用动宾短语:「添加 xxx」「修复 xxx」「优化 xxx」
    • 不加句号结尾
    • 不要写「修改了代码」这种无意义描述
好的示例
feat(权限): 添加基于 RBAC 的细粒度权限控制
fix(支付): 修复微信支付回调签名验证失败的问题
perf(列表页): 优化大数据量表格的虚拟滚动渲染
refactor(网关): 将单体网关拆分为独立微服务
反面示例
# 以下写法应避免
fix: 修了一个 bug
feat: 更新代码
chore: 改了点东西

4. Body 编写规范

Body 用于详细说明本次变更的动机、方案和影响。

编写要点
  • 说明为什么要做这个改动(背景/原因)
  • 说明怎么做的(技术方案摘要)
  • 说明影响范围(哪些模块、接口受影响)
  • 每行不超过 72 个字符(中文约 36 个汉字)
  • 正文与标题之间空一行
Body 模板
<改动背景和原因>

技术方案:
- <方案要点 1>
- <方案要点 2>

影响范围:<受影响的模块或服务>

5. Breaking Changes 标注

当提交包含不兼容变更时,必须在 footer 中标注。

feat(接口): 重构用户信息返回结构

将用户接口返回的扁平结构改为嵌套结构,前端需同步调整字段取值路径。

BREAKING CHANGE: /api/user/info 返回结构变更
- avatar 字段移入 profile 对象
- 移除已废弃的 nickname 字段,统一使用 displayName
格式二:type 后加感叹号
feat(接口)!: 重构用户信息返回结构
团队约定
  • 涉及数据库表结构变更 -> 必须标注 BREAKING CHANGE
  • 涉及公共 API 参数/返回值变更 -> 必须标注
  • 涉及配置文件格式变更 -> 必须标注
  • 标注时须写明迁移方法或升级步骤

6. Issue 关联

GitHub 格式
Closes #128
Refs #129, #130
Gitee 格式
Closes #I5ABC1
相关需求: https://gitee.com/org/repo/issues/I5ABC1
Coding 格式
关联 Coding 缺陷 #12345
fixed=project-2024/issues/678
通用写法
# footer 中关联多个平台
Closes #128
Jira: PROJ-456
禅道: #789

7. Changelog 自动生成配置

安装 conventional-changelog
bash
npm install -D conventional-changelog-cli conventional-changelog-conventionalcommits
package.json 脚本
json
{
  "scripts": {
    "changelog": "conventional-changelog -p conventionalcommits -i CHANGELOG.md -s",
    "changelog:all": "conventional-changelog -p conventionalcommits -i CHANGELOG.md -s -r 0",
    "release": "standard-version"
  }
}
.versionrc.js 中文配置
javascript
module.exports = {
  types: [
    { type: 'feat', section: '新功能' },
    { type: 'fix', section: '缺陷修复' },
    { type: 'perf', section: '性能优化' },
    { type: 'refactor', section: '代码重构' },
    { type: 'docs', section: '文档更新' },
    { type: 'test', section: '测试' },
    { type: 'chore', section: '构建/工具', hidden: true },
    { type: 'ci', section: '持续集成', hidden: true },
    { type: 'style', section: '代码格式', hidden: true }
  ],
  commitUrlFormat: '{{host}}/{{owner}}/{{repository}}/commit/{{hash}}',
  compareUrlFormat: '{{host}}/{{owner}}/{{repository}}/compare/{{previousTag}}...{{currentTag}}'
}

8. commitlint 中文配置

安装
bash
npm install -D @commitlint/cli @commitlint/config-conventional
commitlint.config.js
javascript
module.exports = {
  extends: ['@commitlint/config-conventional'],
  rules: {
    'type-enum': [2, 'always', [
      'feat', 'fix', 'docs', 'style', 'refactor',
      'perf', 'test', 'chore', 'ci', 'revert'
    ]],
    'type-case': [2, 'always', 'lower-case'],
    'type-empty': [2, 'never'],
    'subject-empty': [2, 'never'],
    'subject-max-length': [2, 'always', 100],
    // 允许中文字符,关闭 subject-case 限制
    'subject-case': [0],
    // 关闭 header-max-length 或放宽(中文占宽较大)
    'header-max-length': [2, 'always', 120],
    'body-max-line-length': [1, 'always', 200],
    'footer-max-line-length': [1, 'always', 200]
  },
  prompt: {
    messages: {
      type: '选择提交类型:',
      scope: '输入影响范围(可选):',
      subject: '填写简短描述:',
      body: '填写详细描述(可选,使用 "|" 换行):',
      breaking: '列出不兼容变更(可选):',
      footer: '关联的 Issue(可选,例如 #123):',
      confirmCommit: '确认提交以上信息?'
    }
  }
}

9. husky + lint-staged 集成

安装与初始化
bash
npm install -D husky lint-staged
npx husky init
配置 commit-msg 钩子
bash
# .husky/commit-msg
npx --no -- commitlint --edit "$1"
配置 pre-commit 钩子
bash
# .husky/pre-commit
npx lint-staged
lint-staged 配置(package.json)
json
{
  "lint-staged": {
    "*.{js,ts,jsx,tsx,vue}": [
      "eslint --fix",
      "prettier --write"
    ],
    "*.{css,scss,less}": [
      "stylelint --fix",
      "prettier --write"
    ],
    "*.md": [
      "prettier --write"
    ]
  }
}
交互式提交(可选)
bash
npm install -D commitizen cz-conventional-changelog

# package.json 中添加
{
  "config": {
    "commitizen": {
      "path": "cz-conventional-changelog"
    }
  },
  "scripts": {
    "commit": "cz"
  }
}

运行 npm run commit 即可进入交互式提交引导。

10. 团队规范检查清单

提交前自查
  • type 是否正确选择(feat/fix/docs/...)
  • scope 是否准确描述了影响模块
  • subject 是否为动宾短语且不超过 50 字符
  • subject 末尾是否去掉了句号
  • body 是否说明了变更原因和方案
  • 不兼容变更是否标注了 BREAKING CHANGE
  • 相关 Issue 是否已关联
  • 一次提交是否只做了一件事(原子性)
团队落地步骤
  1. 工具链配置:按上述步骤配置 commitlint + husky,让规范可执行
  2. 模板共享:将 .commitlintrc、.husky/ 等配置提交到仓库
  3. 团队培训:组织 15 分钟的规范说明会,演示工具使用
  4. Code Review:Review 时关注 commit message 质量
  5. 持续迭代:每季度回顾规范执行情况,根据团队反馈调整
常见问题

Q: 中英文混排时空格怎么处理? A: 中文与英文/数字之间加一个空格,如「添加 Redis 缓存」。

Q: scope 用中文还是英文? A: 团队内统一即可。推荐中文(可读性好),但需在 commitlint 中关闭 scope-case 检查。

Q: 多人协作时如何保证规范一致? A: 靠工具而非靠自觉。配置好 husky + commitlint,不符合规范的提交会被拦截。

© jnMetaCode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/chinese-commit-conventions of jnMetaCode/superpowers-zh.

Open the folder on GitHubat commit fe34019

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jnMetaCode/superpowers-zh, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Chinese Commit Conventions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Chinese Commit Conventions compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chinese Commit Conventions this skilljnMetaCode/superpowers-zh8.3k1 repos~1.6kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Releasequerylenshq/ef-querylens225—~887Automated safety check: PassMIT
Codemie Releasecodemie-ai/codemie-code294—~1.8kAutomated safety check: PassApache-2.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT

Similar skills

  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Release

    querylenshq/ef-querylens

    A skill your agent uses when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub…

    225 GitHub stars~887 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Codemie Release

    codemie-ai/codemie-code

    Release a new version of CodeMie CLI. An agent skill from codemie-ai/codemie-code.

    294 GitHub stars~1.8k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from jnMetaCode/superpowers-zh

All 21 skills in this repo
  • Brainstorming Before Building

    jnMetaCode/superpowers-zh

    Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.

    8.3k GitHub stars~1.8k tokensUpdated 4 days ago
    Auto-check passed
  • Inline Plan Execution

    jnMetaCode/superpowers-zh

    Executes a written implementation plan task by task in the current session, with a progress ledger, test-first gates and one fresh-context review at the end.

    8.3k GitHub stars~2.5k tokensUpdated 4 days ago
    Auto-check passed
  • Git Worktree Isolation

    jnMetaCode/superpowers-zh

    Sets up an isolated workspace before feature work or plan execution, preferring native worktree tools and falling back to git worktree, with instructions in Chinese.

    8.3k GitHub starsUsed in 1 repo~982 tokens
    Auto-check passed
  • Agency Orchestrator Workflow Runner

    jnMetaCode/superpowers-zh

    Runs agency-orchestrator YAML workflows inside the current agent session, with the session's own model playing each role in turn and no API key needed.

    8.3k GitHub starsUsed in 1 repo~885 tokens
    Auto-check passed
  • Chinese Code Review Etiquette

    jnMetaCode/superpowers-zh

    Gives Chinese-language templates and priority labels for code review feedback, plus guidance on bilingual comments, commit messages and common team anti-patterns.

    8.3k GitHub stars~1.2k tokensUpdated 4 days ago
    Auto-check passed
  • Chinese Documentation Style Guide

    jnMetaCode/superpowers-zh

    Reference rules for typesetting Chinese technical documents: spacing around English and digits, punctuation, term handling, bilingual API docs and README layout.

    8.3k GitHub stars~1.6k tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Chinese Commit Conventions

What does Chinese Commit Conventions do?

Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms. 0 for Chinese-speaking teams. Ten types are defined with example scenarios: feat, fix, docs, style, refactor, perf, test, chore, ci and revert.

When should I use Chinese Commit Conventions?

Chinese Commit Conventions fits situations like: writing git commit messages in Chinese with a consistent structure; setting up commitlint, husky or commitizen for a Chinese-speaking team; linking commits to GitHub, Gitee or Coding issues; marking breaking changes together with migration steps.

How do I install Chinese Commit Conventions in Claude Code?

Run `npx skills add jnMetaCode/superpowers-zh --skill chinese-commit-conventions -a claude-code`. Or copy the skill folder (skills/chinese-commit-conventions in jnMetaCode/superpowers-zh) into .claude/skills/chinese-commit-conventions in your project. Claude Code loads it when a task matches its description.

How do I install Chinese Commit Conventions in Codex?

Run `npx skills add jnMetaCode/superpowers-zh --skill chinese-commit-conventions -a codex`. Or copy the skill folder (skills/chinese-commit-conventions in jnMetaCode/superpowers-zh) into .agents/skills/chinese-commit-conventions in your project. Codex loads it when a task matches its description.

Can I use Chinese Commit Conventions in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jnMetaCode/superpowers-zh --skill chinese-commit-conventions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chinese-commit-conventions, .gemini/skills/chinese-commit-conventions, .github/skills/chinese-commit-conventions and .opencode/skills/chinese-commit-conventions in your project.

What does Chinese Commit Conventions need to run?

Going by SKILL.md and its folder, Chinese Commit Conventions needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js tooling, if you adopt commitlint, husky or commitizen.

Does Chinese Commit Conventions access the network?

SKILL.md names 1 domain. In commands or code: gitee.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Chinese Commit Conventions safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Chinese Commit Conventions use?

Chinese Commit Conventions is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Chinese Commit Conventions use?

About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Chinese Commit Conventions?

Skills that share tags, products or a category with Chinese Commit Conventions: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Release (querylenshq/ef-querylens, 225 stars), Codemie Release (codemie-ai/codemie-code, 294 stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chinese Commit Conventions?

jnMetaCode (a GitHub user) maintains it in jnMetaCode/superpowers-zh, which has 8,270 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 4, 2026.

Source: jnMetaCode/superpowers-zh on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.