chinese-commit-conventions

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

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/chinese-commit-conventions/SKILL.md

Quality

Content

65%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.

A highly actionable, well-structured Chinese commit-conventions reference whose configs are copy-paste ready, but it is somewhat redundant with Claude's existing Conventional Commits knowledge, lacks verification checkpoints in its setup workflow, and uses no progressive disclosure to split reference material into separate files.

Suggestions

Trim restatements of standard Conventional Commits mechanics (type meanings, BREAKING CHANGE/! notation) and keep only the Chinese-adaptation specifics to improve conciseness.

Add a verification checkpoint to the toolchain setup (e.g., after configuring commitlint+husky, run a sample invalid commit and confirm it is rejected) to raise workflow clarity.

Move the full config blocks (commitlint.config.js, .versionrc.js) and the FAQ into a references/ file linked from SKILL.md so the overview stays lean and progressive disclosure is applied.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but several sections restate standard Conventional Commits knowledge Claude already has (the feat/fix/docs type meanings, the <type>(<scope>): <subject> template, BREAKING CHANGE footer and ! notation); the Chinese-adaptation constraints and config snippets are the genuine value-add that keep it from scoring lower.	3 / 5
Actionability	Provides fully copy-paste-ready, executable artifacts — commitlint.config.js, .versionrc.js, package.json scripts, husky hooks, lint-staged and commitizen configs — plus concrete good/bad commit examples covering the common cases.	5 / 5
Workflow Clarity	The 团队落地步骤 gives a sequenced 5-step rollout and a pre-commit checklist, but the toolchain setup sections (install → config → hooks) lack any validation/verify checkpoint to confirm the config actually works.	3 / 5
Progressive Disclosure	Internal structure is good (10 numbered, headed sections) but the skill is a single ~360-line file with no bundle files and no one-level-deep references; detailed configs and the FAQ that could live in separate reference files are all inlined.	3 / 5
	Total	14 / 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.

The description is specific, well-triggered, and clearly distinct: it states concrete deliverables, an explicit invocation trigger, and a guard against auto-firing. Minor synonym coverage is the only gap.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete capabilities — "Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置" — naming distinct tools and deliverables, though framed as config areas rather than actions, leaving minor coverage gaps versus a fully comprehensive action list.	4 / 5
Completeness	Clearly answers both 'what' (中文 commit 与 changelog 配置参考 plus three named config areas) and 'when' with a concrete trigger phrase ("仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发").	5 / 5
Trigger Term Quality	Good keyword coverage with natural domain terms (commit, changelog, Conventional Commits, commitlint, husky, commitizen) plus the explicit /chinese-commit-conventions trigger, but a few natural synonyms like 提交信息/git 提交规范 are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Chinese-adaptation niche and the explicit non-auto-trigger clause ("不要根据上下文自动触发") minimizes overlap with generic commit-convention skills.	5 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: c68725b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.