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.

1.02x

Quality

88%

Does it follow best practices?

Impact

94%

1.02x

Average score across 5 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is spec-driven-magic/sdx-commit

Quality

Content

90%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.

The body is concise, highly actionable, and well-structured with a clear sequenced workflow and confirmation/verification checkpoints. The main gap is the absence of an explicit error-recovery loop for failed commits in this batch operation.

Suggestions

Add an explicit feedback loop in Step 5 for commit failures (e.g., if `git commit` fails, surface the error, fix the cause, and re-run) to strengthen validation for this batch operation.

Clarify the expected handling when `git add` for a group fails or partially stages (e.g., re-check `git status --porcelain` and confirm the group's files before committing).

Consider noting what to do if the working tree becomes dirty mid-run (e.g., unexpected changes appear between commits) to close the remaining workflow validation gap.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: numbered steps with copy-paste bash commands, terse rules, and examples, with no explanation of git or commit concepts Claude already knows — every token earns its place.	5 / 5
Actionability	Provides fully executable, copy-paste-ready commands (git status, git add, git commit, git log) plus a concrete commit-message format with single- and multi-line examples covering the common cases.	5 / 5
Workflow Clarity	A clear 6-step sequence with explicit checkpoints (confirmation gate before committing, staged-summary review, clean-index check, final verification via git log), but it lacks an explicit error-recovery feedback loop for failed commits, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Well-organized into three clear sections with no bundle files inlined inappropriately; content is appropriately self-contained in a single file, though no one-level-deep references exist to signal, which keeps it just below the 5 anchor.	4 / 5
	Total	18 / 20 Passed

Description

87%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 that concretely states what the skill does and gives explicit, natural trigger phrases for when to use it. Only minor synonym coverage is missing from the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete actions — "Analyzes git changes", "groups them by logical change or OpenSpec feature", "creates conventional commits for each group" — with only minor coverage gaps, matching the anchor listing several specific actions.	4 / 5
Completeness	Clearly answers both what (analyze, group, create conventional commits) and when with explicit concrete trigger phrases in the "Use when..." clause, matching the anchor that requires both answered explicitly.	5 / 5
Trigger Term Quality	Includes natural developer phrases ("organizing staged changes", "splitting commits into atomic units", "structured commits instead of one mixed commit") with good coverage, though it omits common synonyms like "commit messages" and "git commit" that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — grouping git changes into conventional commits tied to OpenSpec features — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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/skills/sdx-commit/SKILL.md
Commit: 9086596

Reviewed: 17 hours ago

Table of Contents

Discovery Implementation Validation

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.