CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-commit

Use this skill whenever the user asks to write, draft, review, or make a git commit, or asks to commit changes to version control ("haz un commit", "redacta el commit", "hacer commit", "commit y push", "guardar cambios en git").

Quality

84%

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

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.

A well-structured, actionable workflow with concrete git commands, a clear message template, and appropriate safety checks for secrets. The main gaps are minor: slight over-explanation of standard Conventional Commits rules and a commit command that cannot emit the multi-line message body it prescribes.

Suggestions

Replace git commit -m "<mensaje>" with a multi-line-capable invocation (e.g., a heredoc or multiple -m flags) so the command can produce the bulleted body the template requires.

Trim the intro paragraph and the Conventional Commits rules Claude already knows (72-char limit, imperative mood), keeping only the project-specific type mappings (e.g., Tailwind under 'style').

Add a lightweight post-commit verification step (e.g., confirm with git log -1 --stat) to close the workflow with an explicit checkpoint.

DimensionReasoningScore

Conciseness

Mostly lean procedural content with concrete commands and template, but the opening framing sentence and the restatement of standard Conventional Commits rules (72-char title, imperative mood) explain conventions Claude already knows, matching the 'minor instances of over-explanation that could be trimmed' anchor.

4 / 5

Actionability

Provides executable commands throughout (git status, git diff --staged, git add, git commit -m, git push origin) plus a concrete message template, matching the 'mostly executable guidance with minor gaps' anchor. Not 5 because a single git commit -m "<mensaje>" cannot produce the multi-line bulleted body the template specifies.

4 / 5

Workflow Clarity

Clear three-step sequence (inspect diff, draft message, confirm-and-execute) with a user-confirmation checkpoint and a secrets safety pre-check, matching the 'clear sequence with most checkpoints present; minor validation gaps' anchor. Not 5 because there is no post-commit verification or explicit feedback loop.

4 / 5

Progressive Disclosure

A simple single-purpose skill (~58 lines) with no bundle files and nothing that belongs in a separate reference; clean, well-signaled section headers fully organize the content, which per the simple-skill guidance earns the top anchor.

5 / 5

Total

17

/

20

Passed

Description

82%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 strong description with excellent bilingual trigger coverage and an explicit 'Use whenever' clause. Its main weakness is that the capability statement (the 'what') is folded into the trigger clause and omits the skill's actual methodology (Conventional Commits message drafting).

DimensionReasoningScore

Specificity

Lists several concrete actions ("write, draft, review, or make a git commit", "commit changes to version control") matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the actions are near-synonyms of one task and the description omits capabilities the body actually delivers (Conventional Commits formatting, push).

4 / 5

Completeness

The 'when' is explicit with concrete trigger phrases, and the 'what' (write, draft, review, or make a git commit) is present but embedded in the when-clause rather than stated as a dedicated capability statement. Not 5 because the what lacks detail on what the skill actually produces (e.g., Conventional Commits messages).

4 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms in both English and Spanish ("haz un commit", "redacta el commit", "hacer commit", "commit y push", "guardar cambios en git"), matching the 'comprehensive coverage of natural terms including synonyms' anchor.

5 / 5

Distinctiveness Conflict Risk

Clear git-commit niche with distinct triggers, but the trigger "review... a git commit" creates minor overlap risk with code-review skills, matching the 'mostly distinct; minor overlap risk' anchor rather than the minimal-conflict anchor at 5.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

CRISOMG/Cris-Site

Path

.agents/skills/git-commit/SKILL.md

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.