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.
80
100%
Does it follow best practices?
Impact
—
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 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 focus on staged changes and commit creation makes it distinct from general code review or git branching 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 clear validation checkpoints, concrete commands, and explicit guardrails. The Review Suppressions section is a particularly thoughtful addition that reduces false positives. The content is appropriately scoped and structured for its purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. Every section serves a purpose—no explanations of what git is, what conventional commits are, or how npm works. It trusts Claude's intelligence and keeps instructions tight. | 3 / 3 |
Actionability | Provides concrete, executable bash commands for each step, specific commit message format with examples of types, explicit file staging commands, and clear checklists for code review scanning. The guidance is copy-paste ready. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with quality gates as explicit validation checkpoints before committing. The guardrails section enforces constraints (never skip quality gates, never use `git add .`), and the code review scan acts as a feedback loop before proceeding to commit. | 3 / 3 |
Progressive Disclosure | For a standalone skill with no bundle files, the content is well-organized into clearly labeled sections (Workflow, Commands, Code Review Scan, Commit Message Format, Guardrails, Output, Review Suppressions). Each section is appropriately sized and easy to navigate without needing external references. | 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
9fc35f5
- 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.