生成符合 Conventional Commits 规范的 Git 提交信息。当用户要求生成提交、创建 commit 或写提交信息时使用
91
Quality
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description that clearly defines its purpose and includes explicit trigger conditions in Chinese. The main weakness is the lack of specific action details - it could benefit from listing concrete capabilities like analyzing staged changes or formatting commit types. Overall, it's functional and would enable accurate skill selection.
Suggestions
Add specific actions like 'analyzes git diffs', 'formats commit headers with type/scope', or 'generates body and footer sections' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Git commit messages) and mentions Conventional Commits standard, but doesn't list specific actions like analyzing diffs, formatting headers, or handling different commit types. | 2 / 3 |
Completeness | Clearly answers both what (generates Conventional Commits compliant Git commit messages) and when (explicit '当用户要求...' clause with specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes natural Chinese trigger terms users would say: '生成提交' (generate commit), '创建 commit' (create commit), '写提交信息' (write commit message). Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Git commit messages with Conventional Commits standard. Distinct triggers like 'commit', '提交信息' make it unlikely to conflict with general code or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides clear, actionable guidance for generating conventional commit messages. The type definitions and example are excellent. The main weakness is the lack of validation steps or guidance for edge cases (empty diff, mixed change types, verification before commit).
Suggestions
Add a validation step: after generating the message, verify it meets the 50-char subject limit and format requirements before presenting to user
Add guidance for edge cases: what to do when changes span multiple types, or when the staging area is empty
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information. Type definitions are terse, steps are minimal, and there's no explanation of concepts Claude already knows (like what git is or how commits work). | 3 / 3 |
Actionability | Provides concrete executable command (`git diff --cached`), specific format rules, clear type definitions, and a complete example output. The guidance is specific enough to be immediately actionable. | 3 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. There's no guidance on what to do if the diff is empty, if changes span multiple types, or how to verify the generated message meets the quality standards before committing. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (task, spec, steps, standards, example). No external references needed for this scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
b1b2fe0
Table of Contents
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.