commit
Semantic commit format, branch naming, squashing guidance, and post-commit memory check
70
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./dot_config/opencode/skill/commit/SKILL.mdQuality
Discovery
32%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 provides a list of topic areas rather than concrete actions, reads more like a table of contents than a functional description. It completely lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill. The term 'post-commit memory check' is ambiguous and could confuse skill selection.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'git commit', 'commit message', 'branch name', 'conventional commits', 'squash commits'.
Rewrite as concrete actions in third person, e.g., 'Generates semantic commit messages following conventional commit format, suggests branch naming conventions, provides squashing guidance for git history cleanup.'
Clarify what 'post-commit memory check' means in plain language so Claude can accurately match user requests to this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git/version control) and lists some actions like 'semantic commit format', 'branch naming', 'squashing guidance', and 'post-commit memory check', but these are more like topic labels than concrete actions (e.g., 'generates semantic commit messages' would be more specific). | 2 / 3 |
Completeness | Describes what the skill covers at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also only loosely described, this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'commit', 'branch naming', and 'squashing', which users might naturally mention. However, it misses common variations like 'git', 'commit message', 'conventional commits', 'merge', or 'version control'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of semantic commits, branch naming, squashing, and memory check is somewhat distinctive, but 'commit format' and 'branch naming' could overlap with general git workflow skills. The 'post-commit memory check' is unique but unclear. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides clear, actionable guidance for commit workflows. It's concise, well-structured with logical sections, and includes executable examples throughout. The only minor weakness is that all content is inline rather than using progressive disclosure to separate the core commit format from ancillary concerns like PR descriptions and issue traceability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what git is or how commits work. The tables, examples, and bash snippets all earn their place without padding. | 3 / 3 |
Actionability | Provides concrete, executable commands (git add -A, git check-ignore, git branch -m), specific commit message examples, and clear naming conventions. The pre-commit checklist and branch renaming snippet are copy-paste ready. | 3 / 3 |
Workflow Clarity | The 'Before Every Commit' section is a clearly sequenced workflow with validation (run tests, check ignored files). Squashing guidance distinguishes before-first-push vs after-review scenarios. The post-commit memory check provides a decision framework. Branch renaming includes a conditional check before acting. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's moderately long and entirely inline. The 'learn' skill is referenced but other potential references (e.g., linking to a detailed PR template or test suite docs) are absent. Some sections like PR Descriptions and Issue Traceability could potentially be split out. | 2 / 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.
- Repository
- athal7/dotfiles
- Commit
4ed3a13
- 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.