CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commit

ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.

Quality

86%

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.

The content is highly actionable with a validated branch-safety workflow, a concrete format specification, and copy-paste-ready examples that cover common cases including reverts and breaking changes. Its main gaps are mild redundancy with widely known conventional-commit conventions and the absence of a final check that the produced message satisfies the stated length rules.

DimensionReasoningScore

Conciseness

The body is efficient — branch-safety commands, Sentry-specific type entries (ref, meta, license), issue-reference patterns, and full examples all earn their place — but the standard conventional-commit types (feat, fix, docs, ci, chore, style), imperative subject rules, and 'explain what and why' guidance re-teach what Claude already knows, matching anchor 4's minor over-explanation.

4 / 5

Actionability

Guidance is fully executable: concrete commands ('git branch --show-current'), an exact header template, copy-paste footer patterns, and four complete example commit messages plus a revert format that cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

The branch-safety workflow has a clear sequence with an explicit checkpoint ('verify the current branch has changed before proceeding') and an abort path ('If still on main or master ... stop — do not commit'), but there is no validation of the produced message against the stated rules (70-char subject, 100-char lines), matching anchor 4 rather than 5.

4 / 5

Progressive Disclosure

With no bundle files, the single SKILL.md is well organized into clear sections with the external link properly placed under References; at ~166 lines it exceeds the under-50-line simple-skill exception, and the lengthy examples section could arguably live in a reference file, matching anchor 4.

4 / 5

Total

17

/

20

Passed

Description

86%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 with an explicit trigger clause and a concrete statement of what the skill produces. Its main weaknesses are modest action coverage (missing branch safety and the commit-type taxonomy) and a universal 'ALWAYS' trigger that slightly raises conflict risk with generic commit skills.

DimensionReasoningScore

Specificity

The description names the domain and a couple of concrete actions — 'Creates commits following Sentry conventions with proper conventional commit format and issue references' — but omits branch safety, commit types, and footer/breaking-change conventions that the skill body actually covers, matching anchor 3 rather than the minor-gaps profile of anchor 4.

3 / 5

Completeness

It clearly answers both 'what' ('Creates commits following Sentry conventions with proper conventional commit format and issue references') and 'when' with explicit concrete trigger phrases ('Trigger on any commit, git commit, save changes, or commit message task'), matching anchor 5.

5 / 5

Trigger Term Quality

Trigger terms 'commit, git commit, save changes, or commit message task' plus 'committing code changes' comprehensively cover the natural phrasings users would say for this task, including the literal command, verb/noun forms, and a common paraphrase, matching anchor 5.

5 / 5

Distinctiveness Conflict Risk

The Sentry-conventions niche is clearly distinct with specific triggers, but 'ALWAYS use this skill when committing code changes — never commit directly without it' claims every commit task and is not scoped to Sentry repos, creating minor overlap risk with generic commit-message skills — anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/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.