commit

Create git commits for changes made during the session.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/commit/SKILL.md

Quality

Content

78%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 a lean, mostly executable instruction set with a clear sequenced workflow and a user-confirmation checkpoint, well-structured for a simple single-purpose skill. Its main weaknesses are a slightly redundant closing section, vague handling of missing pre-commit hooks, and no concrete commit-message example.

Suggestions

Tighten the '## Remember' section, which restates context Claude already holds (e.g. 'You have the full context of what was done in this session').

Replace the vague 'If rules like pre-commit are missing, solve them' with a concrete fallback (e.g. 'if pre-commit is not installed, run hooks manually or skip with a noted reason').

Add one short example commit message in the planning step to model the imperative-mood style the skill requests.

Dimension	Reasoning	Score
Conciseness	The body is tight and assumes Claude's competence (no preamble explaining what git or commits are); the main over-explanation is the '## Remember' section reiterating context the model already holds, which keeps it just below a 5.	4 / 5
Actionability	It gives concrete executable commands (git status, git diff, pre-commit run --all-files, git add with specific files, git log --oneline) and a literal confirmation prompt; minor gaps (no example commit-message format) hold it at 4 rather than 5.	4 / 5
Workflow Clarity	A clear four-step sequence with a user-confirmation checkpoint and an explicit verification step (git log --oneline), but it relies on a confirmation gate rather than a validate-fix-retry loop and the pre-commit instruction ('solve them') is vague, so it stays at 4.	4 / 5
Progressive Disclosure	For a short single-purpose skill with no external references needed, the content is well-organized into clearly headed sections (Process, Important, Remember); per the simple-skill scoring note this qualifies for 5 without bundle files.	5 / 5
	Total	17 / 20 Passed

Description

53%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 states the core action clearly and is appropriately concise, but it omits any explicit 'Use when' trigger guidance and lacks the natural user phrases and synonyms that would make discovery reliable. It is a solid mid-range description with room to add a trigger clause.

Suggestions

Add a 'Use when...' clause naming natural user phrases such as 'commit my changes', 'write commit messages', or 'save my session work' to lift completeness and trigger coverage.

Broaden keyword coverage beyond 'git commits' to include synonyms like 'commit messages' and 'staging changes' for stronger trigger-term quality.

Optionally mention the supporting actions (review diffs, plan atomic commits) to make capabilities more comprehensive.

Dimension	Reasoning	Score
Specificity	The phrase 'Create git commits for changes made during the session' names the domain (git commits) and one concrete action (create commits), matching the 'Names domain and 1-2 concrete actions, but not comprehensive' anchor; it does not enumerate the supporting actions the body covers (diff review, commit planning, pre-commit).	3 / 5
Completeness	It has a clear 'what' (create git commits for session changes) but no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness caps at 3.	3 / 5
Trigger Term Quality	'git commits' and 'changes made during the session' are relevant but it omits the natural phrases users say ('commit my changes', 'write commit messages', 'save my work'); coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	'Create git commits' carves a reasonably clear niche distinct from most skills with only minor overlap risk against adjacent version-control or git-workflow skills; it does not reach the fully explicit-trigger anchor of 5.	4 / 5
	Total	13 / 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: pymc-labs/pymc-marketing
Path: .cursor/skills/commit/SKILL.md
Commit: 66d575d

Reviewed: 4 days 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.