CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chinese-commit-conventions

中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用,不要根据上下文自动触发。

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable reference material with copy-paste configs, complete examples, and a useful team checklist, but the single monolithic file inlines toolchain setup that belongs in reference files, and it re-explains standard Conventional Commits knowledge Claude already has. Splitting tool configs into references/ and trimming to the Chinese-specific deltas would lift both conciseness and progressive disclosure.

Suggestions

Move sections 7–9 (conventional-changelog, commitlint, husky/lint-staged/commitizen setup) into a references/ file such as TOOLCHAIN.md, keeping SKILL.md as a concise conventions overview with clearly signaled one-level-deep links.

Trim content Claude already knows — the standard 10-type table, BREAKING CHANGE footer syntax, and GitHub 'Closes #N' format — and keep only the Chinese-specific deltas (English type + Chinese scope/subject, Gitee/Coding link formats, commitlint rule adjustments for Chinese).

Add a validation step to the toolchain setup workflow, e.g. confirming commitlint works by piping an invalid message ('echo "bad message" | npx commitlint') and expecting it to fail before relying on the hook.

DimensionReasoningScore

Conciseness

Sections 1, 5, and 6 re-explain standard knowledge Claude already has — the full 10-type Conventional Commits table, BREAKING CHANGE footer/`!` notation, and GitHub 'Closes #128' syntax — where only the Chinese deltas (English type + Chinese scope/subject, Gitee/Coding formats) add value. Prose is minimal and mostly tables/configs, so this is 'some unnecessary explanation' (anchor 3) rather than heavily padded (anchor 2) or merely minor trimming (anchor 4).

3 / 5

Actionability

Fully copy-paste ready: install commands, complete commitlint.config.js, .versionrc.js, package.json scripts, husky hook and lint-staged configs, full commit message examples, and a body template. Specific examples cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

Setup (install → husky init → hooks) and the 5-step 团队落地 rollout are clearly sequenced, and the 提交前自查 checklist plus commitlint enforcement provide checkpoints. A verification step for the toolchain (e.g., testing with an intentionally invalid message) is absent — anchor 4's 'most checkpoints present, minor validation gaps'.

4 / 5

Progressive Disclosure

~370 lines all inlined in SKILL.md with no bundle files; sections 7–9 (~140 lines of tool configuration) clearly belong in separate reference files. Numbered sections make it navigable (above anchor 2's minimal structure), but bulk content that should be separate is inline (anchor 3 rather than 4).

3 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names the niche (Chinese-localized commit/changelog conventions and tooling) with specific tools, and gives an explicit, concrete trigger condition with an anti-drift clause. The only weaknesses are mild — noun-phrase capability listing and a few missing natural synonyms like '提交规范' or 'commit message'.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas —「Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置」— naming the domain plus specific tooling, though as noun phrases with minor gaps (checklist/FAQ content unmentioned). It falls short of anchor 5's verb-driven comprehensive action coverage, but exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Both 'what' (中文 commit 与 changelog 配置参考 covering three named areas) and 'when' (「仅在用户显式 /chinese-commit-conventions 时调用,不要根据上下文自动触发」) are explicitly and concretely answered. The trigger is fully explicit with a concrete slash-command phrase, so it matches anchor 5 rather than anchor 4's 'when could be more specific'.

5 / 5

Trigger Term Quality

Natural domain keywords are present: 'commit', 'changelog', 'Conventional Commits', 'commitlint', 'husky', 'commitizen', 'conventional-changelog', plus '中文'. Common variations a user would naturally say ('git 提交', '提交规范', 'commit message') are missing, matching anchor 4's 'good keyword coverage; a few natural terms missing' rather than anchor 5's synonym-complete coverage.

4 / 5

Distinctiveness Conflict Risk

A clear Chinese-localization niche with distinct tool names, plus a trigger restricted to an explicit slash command with an explicit 'do not auto-trigger' clause — minimal conflict risk with any similar skill, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

jnMetaCode/superpowers-zh

Path

skills/chinese-commit-conventions/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.