CtrlK
BlogDocsLog inGet started
Tessl Logo

dev-commit

AI DevKit · Safe git commit workflow for AI coding agents. Use when the user asks to commit, prepare a commit, stage changes, create a PR-ready checkpoint, or finish work with a conventional commit while avoiding unrelated user changes.

76

Quality

93%

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

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

An exemplary instruction-only skill body: lean, concrete, and well-sequenced with validation checkpoints and feedback loops. No bundle files exist and none are needed for this scope.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: every line is an instruction or a concrete git command, with no over-explanation of git or conventional-commit concepts Claude already knows.

5 / 5

Actionability

Fully executable guidance with copy-paste-ready commands (`git status --short --branch`, `git diff --cached`, `git add path/to/file`) and a concrete conventional-commit format plus a type list covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced 7-step Commit Contract with an explicit validation checkpoint (step 3) and a re-check checkpoint (step 5), plus Guardrails feedback loops for validation failure and hook failures; the destructive operation has the required validation.

5 / 5

Progressive Disclosure

A single-purpose skill under 50 lines with no bundle files and no need for external references, organized into clear sections (Commit Contract, Guardrails, Message Style), meeting the simple-skill exception for a top score.

5 / 5

Total

20

/

20

Passed

Description

87%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 well-constructed description: third-person, concrete actions, an explicit 'Use when' trigger clause with natural phrasing, and a distinctive scope. Minor room to add a couple more natural synonyms for completeness and trigger coverage.

DimensionReasoningScore

Specificity

Names several concrete actions ('commit', 'prepare a commit', 'stage changes', 'create a PR-ready checkpoint', 'finish work with a conventional commit'), matching the several-specific-actions anchor with minor coverage gaps rather than a comprehensive multi-action list.

4 / 5

Completeness

Explicitly states what it does ('Safe git commit workflow for AI coding agents ... avoiding unrelated user changes') and gives an explicit 'Use when...' clause with multiple concrete trigger phrases, satisfying the both-what-and-with-concrete-triggers anchor.

5 / 5

Trigger Term Quality

Covers natural user phrases ('asks to commit', 'prepare a commit', 'stage changes', 'PR-ready checkpoint', 'finish work') with good keyword coverage, though a few synonyms like 'make a commit' or 'save my work' are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped to a git-commit workflow for AI coding agents with the distinguishing 'avoiding unrelated user changes' framing, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
codeaholicguy/ai-devkit
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.