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

87%

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

88%Scale 1-5

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

This is a well-crafted skill that provides clear, actionable commit message conventions with excellent examples and a solid prerequisite workflow that prevents accidental commits to main. The content is well-structured with appropriate use of tables, code blocks, and sections. Minor verbosity in a few explanatory sections keeps it from a perfect conciseness score, but overall it's a strong skill.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient and well-organized. The commit types table, format specification, and examples all earn their place. Minor verbosity in the body guidelines section and some of the explanatory text around AI-generated changes could be tightened, but overall it respects Claude's intelligence.	4 / 5
Actionability	Highly actionable with concrete commit message examples covering multiple scenarios (simple fix, feature, refactor, breaking change, revert). The prerequisite section includes exact bash commands, and the format specification with issue reference patterns is copy-paste ready.	5 / 5
Workflow Clarity	The prerequisite section establishes a clear workflow with validation: check branch → create branch if on main → verify branch changed → proceed or stop. This is a well-defined feedback loop for a potentially destructive operation (committing to main). The rest follows a logical sequence from format to types to examples.	5 / 5
Progressive Disclosure	Good structure with clear sections (Prerequisites, Format, Types, Rules, Examples, etc.) and a reference link to external Sentry docs. It appropriately references the `create-branch` skill. Minor gap: the content is moderately long (~130 lines) and could potentially split the examples into a separate file, but the inline examples are reasonable for a skill of this scope.	4 / 5
	Total	18 / 20 Passed

Description

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

This is a solid skill description with excellent trigger terms and completeness. It clearly communicates when to use the skill and includes natural language triggers. The main weakness is that the specificity of capabilities could be improved — it mentions 'Sentry conventions' and 'conventional commit format' but doesn't detail what specific actions it performs (e.g., analyzing diffs, selecting commit types, formatting scopes).

Suggestions

Add more specific capability details such as 'analyzes git diffs to generate descriptive messages, selects appropriate commit type (fix, feat, chore), and formats scope and breaking change annotations.'

Dimension	Reasoning	Score
Specificity	Names the domain (committing code changes) and mentions 1-2 concrete actions (creates commits following Sentry conventions, proper conventional commit format, issue references), but doesn't elaborate on specific capabilities like analyzing diffs, formatting types, or handling scopes.	3 / 5
Completeness	Clearly answers both 'what' (creates commits following Sentry conventions with conventional commit format and issue references) and 'when' (explicitly lists triggers: 'any commit, git commit, save changes, or commit message task'). Has an explicit trigger clause.	5 / 5
Trigger Term Quality	Includes excellent natural trigger terms: 'commit', 'git commit', 'save changes', 'commit message', 'code changes'. These are exactly the phrases users would naturally say when needing this skill.	5 / 5
Distinctiveness Conflict Risk	Fairly distinct due to the Sentry-specific conventions and conventional commit format focus. Minor overlap risk with generic git skills, but the Sentry convention specificity and explicit commit-only scope help differentiate it.	4 / 5
	Total	17 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/commit/SKILL.md
Commit: debb2ec

Reviewed: 14 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.