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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The content is a lean, executable procedural skill with concrete commands, a clear sequenced workflow, and built-in confirmation/review checkpoints appropriate for batch commit operations. It is well-organized and self-contained.

Suggestions

Add an explicit error-recovery feedback loop in step 5 (e.g., 'if `git diff --cached --stat` shows unexpected files, unstage with `git restore --staged` and regroup before committing').

De-duplicate the `git status --porcelain` call shown in both step 1 and step 2 to tighten the workflow.

Clarify how to handle a failed `git commit` (e.g., pre-commit hook failure) with a retry/fix step.

Dimension	Reasoning	Score
Conciseness	The body is efficient with concrete commands and minimal concept explanation; only minor redundancy (e.g., `git status --porcelain` repeated in steps 1 and 2) could be trimmed.	4 / 5
Actionability	Copy-paste-ready bash commands (`git add --`, `git diff --cached --stat`, `git commit -m`) and concrete single/multi-line commit-message examples cover the common cases fully.	5 / 5
Workflow Clarity	A clear 6-step sequence includes checkpoints (confirmation in step 4, staged-review in step 5b, final verification in step 6) for this batch operation, with only minor gaps in explicit error-recovery feedback loops.	4 / 5
Progressive Disclosure	The skill is self-contained with well-organized sections (Steps, Commit Message Format, Guidelines) and no external references needed; good structure with minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

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

The description is strong, clearly stating both the capability and concrete usage triggers in third person. It distinguishes itself well from generic commit helpers while remaining concise.

Dimension	Reasoning	Score
Specificity	"Analyzes git changes, groups them by logical change or OpenSpec feature, and creates conventional commits for each group" lists several concrete actions (analyze, group, create commits), matching the anchor for several specific actions with minor coverage gaps.	4 / 5
Completeness	It explicitly answers both what ("Analyzes git changes, groups them... and creates conventional commits") and when ("Use when organizing staged changes, splitting commits into atomic units, or creating structured commits") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"organizing staged changes, splitting commits into atomic units, or creating structured commits" are natural phrases users would say, giving good keyword coverage, though synonyms like "commit message" are absent.	4 / 5
Distinctiveness Conflict Risk	Conventional-commit creation grouped by logical change is a fairly distinct niche with clear triggers, with only minor overlap risk against generic git-commit skills.	4 / 5
	Total	17 / 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/SKILL.md
Commit: 9086596

Reviewed: 1 day 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.