smart-commit
Run quality gates, review staged changes for issues, and create a well-crafted conventional commit. Use when saying "commit", "git commit", "save my changes", or ready to commit after making changes.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 strong skill description that clearly communicates what the skill does (quality gates, staged change review, conventional commit creation) and when to use it (with explicit trigger terms). It uses third person voice, is concise, and provides enough specificity to distinguish it from other git-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Run quality gates', 'review staged changes for issues', and 'create a well-crafted conventional commit'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (run quality gates, review staged changes, create conventional commit) and 'when' (explicit 'Use when' clause with specific trigger phrases). Fully complete. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would actually say: 'commit', 'git commit', 'save my changes', and 'ready to commit after making changes'. Good coverage of both technical and casual phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to the git commit workflow with quality gates and conventional commits. The specific mention of 'staged changes', 'conventional commit', and 'quality gates' makes it distinct from general code review or git skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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 skill that efficiently communicates a multi-step commit workflow with concrete commands, clear validation checkpoints, and specific review criteria. The Review Suppressions section is a particularly valuable addition that reduces false positives. The content is appropriately concise while being thoroughly actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It doesn't explain what git is, what conventional commits are conceptually, or how npm works. Every section earns its place with actionable content Claude wouldn't inherently know about this project's specific workflow. | 3 / 3 |
Actionability | Provides concrete, executable bash commands for each step, specific commit message format with types listed, explicit code review checklist items, and clear guardrails. The commands are copy-paste ready and the review criteria are specific enough to act on. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with a logical flow: check state → run quality gates → scan for issues → draft message → commit → prompt for learnings. Validation is explicit (quality gates before commit, code review scan before staging), and guardrails enforce never skipping quality gates. The 'flag any issues before proceeding' instruction creates a feedback loop. | 3 / 3 |
Progressive Disclosure | For a skill under 80 lines with no need for external references, the content is well-organized into clearly labeled sections (Workflow, Commands, Code Review Scan, Commit Message Format, Guardrails, Output, Review Suppressions). Each section is focused and scannable. | 3 / 3 |
Total | 12 / 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
- rohitg00/pro-workflow
- Commit
1de1554
- 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.