commit

Optionally checks, then commits code to the current or a new feature branch.

Quality

73%

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

92%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 tight, well-sequenced commit workflow with concrete commands and explicit validation gates that assume Claude's competence. Its only minor weakness is the absence of a literal commit-message example, which keeps actionability at 4 rather than 5.

Suggestions

Add one concrete commit-message example in conventional format to make step 5 fully copy-paste ready and lift actionability to 5.

Optionally show the exact `git commit -m "..."` invocation form alongside the 'use a plain string' instruction.

Dimension	Reasoning	Score
Conciseness	The body is lean and action-oriented with no padding or explanation of git concepts Claude already knows; every line (parallel status commands, prose-pass gate, conventional-commit rules) earns its place, matching the score-5 anchor.	5 / 5
Actionability	Concrete, executable commands are given throughout (`git status`, `git diff HEAD`, `git log --oneline -10`, `git add`, `git branch`) and referenced skills are named, but no literal copy-paste commit-message example is provided, leaving the minor gap described in the score-4 anchor.	4 / 5
Workflow Clarity	A clear 7-step sequence includes explicit validation checkpoints ('Stop if any checks fail', the prose-pass gate, the secrets guard) with a feedback loop on check failure, matching the score-5 anchor for a destructive/batch operation with validation.	5 / 5
Progressive Disclosure	The skill is under 50 lines with no external bundle files, and content is organized into clear 'Arguments' and 'Steps' sections; per the simple-skills note this warrants a score of 5 without external references.	5 / 5
	Total	19 / 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 uses third person with a clear, specific 'what', but it omits any explicit 'when to use' trigger guidance, which caps completeness and limits trigger-term coverage. It is distinct as a git-commit workflow but would benefit from a trigger clause.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to commit code, save staged changes, or create a commit on a branch.'

Include natural synonyms and the canonical command, e.g. 'commits changes (git commit)' to broaden trigger-term coverage.

Consider listing 1-2 more concrete actions (e.g. 'drafts a conventional-commit message') to lift specificity toward score 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain (git commits) and 1-2 concrete actions ('checks' and 'commits code to the current or a new feature branch'), but does not enumerate several specific actions, matching the score-3 anchor and falling below score 4.	3 / 5
Completeness	It gives a clear 'what' ('Optionally checks, then commits code...') but provides no 'Use when...' trigger clause, and the guidelines cap completeness at 3 when explicit trigger guidance is missing.	3 / 5
Trigger Term Quality	'commits code' is a natural phrase a user would say, but the description omits common variations and synonyms (e.g. 'save changes', 'git commit', 'stage files'), so it sits at the score-3 anchor rather than score 4.	3 / 5
Distinctiveness Conflict Risk	'Commits code to the current or a new feature branch' carves a clear niche with a distinct trigger and minimal overlap risk with other skills, fitting the score-4 anchor; it lacks the fully comprehensive triggers needed for score 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: Consensys-Incorporated/ocap-kernel
Path: .claude/skills/commit/SKILL.md
Commit: 3d5aea9

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