Content
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive but overly verbose guide to creating conventional commits with emoji. Its main weakness is extreme length driven by an exhaustive emoji-type mapping table and repeated explanations. The workflow is reasonably clear but lacks validation checkpoints and concrete git commands, and the entire content would benefit greatly from splitting the emoji reference and examples into separate files.
Suggestions
Extract the emoji-type mapping table into a separate reference file (e.g., EMOJI_REFERENCE.md) and keep only the 8 core types in SKILL.md
Add explicit validation checkpoints in the workflow, such as confirming staged files with the user before committing and verifying the commit message matches the diff
Include concrete git commands in the workflow steps (e.g., `git diff --cached`, `git add -p` for selective staging when splitting commits)
Remove redundant sections — the 'Important Notes' section largely restates the Instructions and 'Best Practices' sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with a massive emoji/commit-type mapping table that could be condensed significantly. The extensive examples section, repeated branch naming explanations, and 'Important Notes' section largely restate what was already covered in the instructions. Many concepts (conventional commits, present tense imperative mood) are things Claude already knows. | 1 / 3 |
Actionability | The workflow steps are reasonably concrete (git status, git diff, git add), but there are no actual executable commands or code snippets for the core logic. Pre-commit checks mention 'pnpm lint or similar depending on the project language' which is vague. The branch creation and commit splitting processes lack specific git commands. | 2 / 3 |
Workflow Clarity | The numbered steps in the Instructions section provide a reasonable sequence, but there are no explicit validation checkpoints or error recovery loops. Step 2 mentions pre-commit checks may fail but the handling is only described in the 'Important Notes' section rather than integrated into the workflow. The commit splitting workflow lacks clear step-by-step staging instructions. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files. The massive emoji mapping table (50+ entries) should be in a separate reference file. The examples, guidelines for splitting, branch naming conventions, and command options are all inline, making the skill very long and hard to scan. | 1 / 3 |
Total | 6 / 12 Passed |