CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sdx-commit

Analyzes git changes, groups them by logical change or OpenSpec feature, and creates conventional commits for each group. Use when organizing staged changes, splitting commits into atomic units, or creating structured commits instead of one mixed commit.

Quality

88%

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

82%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 highly actionable, well-sequenced skill with copy-paste git commands, explicit validation checkpoints, and a concrete commit-message format. The main weaknesses are mild redundancy (repeated commands and grouping rules) and the absence of error-recovery guidance.

Suggestions

Remove the duplicate "git status --porcelain" block (step 2 repeats step 1) and consolidate the grouping preference stated in both step 2 and the Guidelines section.

Add a short error-recovery step (e.g., "git reset --soft HEAD~1" if a commit lands with the wrong group or message) to close the workflow-clarity feedback loop.

Drop the one-line intro before "## Steps" — it duplicates the frontmatter description and adds no new information.

DimensionReasoningScore

Conciseness

The body is mostly lean, but "git status --porcelain" is repeated in steps 1 and 2, and "Prefer multiple small commits over one mixed commit" restates step 2's "Prefer one commit per change group" — minor trimmable redundancy matching the 4 anchor.

4 / 5

Actionability

Every step ships copy-paste commands ("git add -- <file1>", "git commit -m \"<message>\""), a concrete format with a scope list, and worked examples like "feat(connector): add Klaviyo connector with cursor pagination", fully matching the 5 anchor.

5 / 5

Workflow Clarity

The 6-step sequence is clear with checkpoints (staged-summary review via "git diff --cached --stat", user confirmation before committing, final "git log --oneline" verification), so the destructive/batch cap does not apply; however no error-recovery feedback (e.g., what to do if a commit fails) keeps it at the 4 anchor.

4 / 5

Progressive Disclosure

With no bundle files, all content is runtime-essential and organized into clear sections (Steps, Commit Message Format, Guidelines), matching the 4 anchor; the redundant one-line intro duplicating the description and decorative "---" separators are minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

88%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 description in third-person voice that clearly states concrete capabilities and an explicit "Use when..." clause with multiple natural triggers. Its only gaps are a few missing synonyms and minor overlap with adjacent commit-message skills.

DimensionReasoningScore

Specificity

"Analyzes git changes, groups them by logical change or OpenSpec feature, and creates conventional commits for each group" lists multiple concrete actions with comprehensive coverage of the skill's niche, matching the 5 anchor.

5 / 5

Completeness

The description explicitly answers both what ("Analyzes git changes, groups them... creates conventional commits for each group") and when ("Use when organizing staged changes, splitting commits into atomic units, or creating structured commits"), matching the 5 anchor with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like "staged changes", "splitting commits into atomic units", and "one mixed commit" give good trigger coverage, but common variations such as "commit messages" or "atomic commits" are missing, matching the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

"conventional commits", "OpenSpec feature", and "atomic units" carve a distinct niche, but closely related commit-message-generation skills share trigger territory, matching the 4 anchor (mostly distinct, minor overlap risk).

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

xomyakus/spec-native-skills

Path

tiles/sdx-commit/SKILL.md

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.