CtrlK
BlogDocsLog inGet started
Tessl Logo

smart-commit

Stages and commits git changes using semantic commits with logical grouping. Use when the user asks to "commit my changes", "commit these changes", "commit staged files", "commit unstaged files", "commit specific files", "make a commit", "create commits", or /commit. Defaults to staged-only scope. Warns if unstaged changes exist. Groups related changes into separate semantic commits with meaningful titles and body descriptions. Supports three scopes: staged (default), unstaged, or specific files/paths provided by the user.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written, fully executable commit workflow with strong sequencing and genuine validation/feedback loops. The only soft spot is a touch of redundancy in the example/avoid lists, but it is otherwise high quality across all dimensions.

Suggestions

Trim the 'Avoid' filler examples (e.g. 'fix: bug fix', 'chore: update stuff') to one or two, since the positive title/body rules already make the point — this would push conciseness toward the top anchor.

Consider collapsing the two full example commit messages into a single representative example plus a one-line note on bodies, to reduce token cost without losing actionability.

The Phase 5 step about 'unstage others temporarily using git restore --staged' could link briefly to why dependency order matters, but this is minor given the existing clarity.

DimensionReasoningScore

Conciseness

Mostly lean and free of padding (no git/git-concept tutorials), with tight command blocks and an actionable commit format; the 'Avoid' filler examples and two full example bodies add some length that could be trimmed slightly, keeping it just below the maximally lean 5.

4 / 5

Actionability

Fully executable — concrete commands (git status --porcelain, git diff --cached, git add <file>, HEREDOC commit, git restore --staged), a precise message format with types, title/body rules, and good/bad examples covering the common cases.

5 / 5

Workflow Clarity

Five phases are clearly sequenced with explicit checkpoints (git log --oneline -1 to confirm) and a real feedback loop for pre-commit hook failures (read error → fix → re-stage → retry, explicitly forbidding --no-verify), plus enumerated error cases.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; the self-contained body is well-organized into clear Scope Resolution / Phase 1-5 / Error Cases sections, matching 'good structure; minor organization gaps' rather than 5 since there is no progressive reference structure to navigate.

4 / 5

Total

18

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, trigger-rich description that concretely states capabilities and gives numerous natural invocation phrases. It is only slightly short of maximal specificity on the action list, but otherwise exemplary.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Stages and commits git changes', 'Groups related changes into separate semantic commits', 'Warns if unstaged changes exist', 'Supports three scopes' — matching the 'lists several specific actions; minor gaps' anchor rather than the fully exhaustive 5.

4 / 5

Completeness

Explicitly answers both what (stages/commits/groups/warns/scopes) and when via concrete 'Use when the user asks to...' trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural phrases users would actually say — 'commit my changes', 'commit these changes', 'commit staged files', 'commit unstaged files', 'commit specific files', 'make a commit', 'create commits', or /commit — matching the 'comprehensive coverage including synonyms' anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (semantic git commits with logical grouping) with distinct triggers and minimal overlap with other skills; third-person voice is maintained throughout.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MrToxy/claude-skills
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.