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 ./.claude/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 content is a tight, actionable workflow with concrete git commands, a confirmation gate, and a pre-commit validation step, well-organized for a simple single-purpose skill. The main gap is the lack of an explicit validate-fix-retry loop for the final commit and a concrete commit-message example.

Suggestions

Add a short concrete commit-message example (e.g. 'feat(auth): add JWT login') to make the imperative-mood guidance copy-paste ready.

Make the post-commit verification an explicit feedback loop, e.g. after committing run `git log --oneline -n [number]` and confirm each planned commit is present before finishing.

Clarify the pre-commit fallback: 'If pre-commit is not configured, run available linters/tests instead' rather than the ambiguous 'solve them'.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanations of what git or commits are), with only minor over-explanation in the 'Remember' section that restates context already implied by the process, fitting the 'efficient; minor instances that could be trimmed' anchor.	4 / 5
Actionability	It provides concrete, executable commands (`git status`, `git diff`, `pre-commit run --all-files`, `git add` with specific files, `git log --oneline -n [number]`) and a concrete confirmation prompt, with only minor gaps such as not showing an example commit-message format, fitting the 'mostly executable' anchor.	4 / 5
Workflow Clarity	The four-step process is clearly sequenced and includes a confirmation checkpoint plus a pre-commit validation step (`pre-commit run --all-files`) with a fix-if-missing instruction; it stops short of an explicit validate-fix-retry feedback loop for the commit result itself, so it fits 'clear sequence with most checkpoints' rather than the fully explicit 5 anchor.	4 / 5
Progressive Disclosure	This is a short, single-purpose skill under 50 lines with no bundle files (references/, scripts/, assets/ are absent), so per the simple-skill exception its well-organized sections (Process, Important, Remember) earn a 5 with no need for external file references.	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 is concise and names a clear niche (creating git commits), but it lacks an explicit 'Use when...' trigger clause and only states a single concrete action, capping completeness and specificity. It is distinct but would benefit from a trigger phrase.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to commit, save, or finalize session changes.'

List another concrete action to lift specificity, e.g. 'Create git commits and stage specific files for changes made during the session.'

Include natural synonyms users say, such as 'commit my changes', 'stage and commit', or 'save my work to git'.

Dimension	Reasoning	Score
Specificity	It names the domain ('git commits') and one concrete action ('Create'), but 'for changes made during the session' is a scope qualifier rather than additional concrete actions, so coverage is limited to a single action rather than the multiple specific actions a 4 or 5 anchor requires.	3 / 5
Completeness	It gives a clear 'what' (create git commits for session changes) but has no 'Use when...' trigger clause; 'when' is only weakly implied by 'during the session', so per the guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	The natural term 'commit(s)' is present and 'git commits' is a phrase users say, but common variations like 'commit my changes', 'stage and commit', or 'git add/commit' are missing, leaving only partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	'Create git commits' is a clear, narrow niche distinct from most other skills with only minor overlap risk against generic git/version-control skills, fitting the 'mostly distinct; minor overlap risk' anchor better than the score-3 anchor.	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: .claude/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.