git-commit-guidelines

Enforce git commit best practices using gitmoji + Conventional Commits format. TRIGGER when creating commits. Ensures quality-gate passes, prevents issue auto-closing (no Close/Fix keywords), includes Co-Authored-By for AI commits, and requires user approval before committing.

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/git-commit-guidelines/SKILL.md

Quality

Content

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

Highly actionable content with an excellent validated workflow, but materially hurt by heavy redundancy — the format, rules, and examples are repeated across four overlapping sections. Splitting the reference table and example bank into separate files would improve both conciseness and progressive disclosure.

Suggestions

Collapse the duplicated rule statements: keep the format table and 7-step workflow, and remove the DO/DO NOT list and Quick Reference Card which restate the same rules.

Trim the eight example scenarios to two or three representative cases (e.g. a simple fix and a multi-change feature with an issue reference).

Move the Gitmoji Reference Table and example bank into a references file (e.g. GITMOJI.md) and link to it from SKILL.md to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body restates the same rules multiple times — format table, 7-step workflow, DO/DO NOT lists, and a Quick Reference Card all repeat the gitmoji/types/permission rules, and eight full example scenarios pad the file well beyond what two or three would convey.	2 / 5
Actionability	Commands are concrete and copy-paste ready ('npm run quality-gate', 'git status', 'git diff --staged', the HEREDOC git commit block, 'git log -1 --pretty=format:"%h %s"'), with worked examples covering the common commit types.	5 / 5
Workflow Clarity	The 7-step workflow is clearly sequenced with explicit validation checkpoints — mandatory quality-gate with a fix-and-retry loop, mandatory user approval at Step 5, and a post-commit verify step — matching the top anchor for feedback loops.	5 / 5
Progressive Disclosure	Section headers and tables give reasonable in-page structure, but everything lives in a single ~360-line SKILL.md with no external references; the gitmoji table and example bank are exactly the kind of content that belongs in a one-level-deep reference file.	3 / 5
	Total	15 / 20 Passed

Description

76%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 specific, well-scoped description that clearly states capabilities and includes an explicit trigger clause, written in correct third-person voice. Its main weakness is a thin trigger-term set that omits common phrasings users say when asking for a commit.

Suggestions

Broaden the trigger clause to include natural user phrasings: 'Use when the user asks to commit changes, write a commit message, run git commit, or says "commit this".'

Add the file extension / command cue 'git commit' explicitly so the description matches the exact command users invoke.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'enforce git commit best practices using gitmoji + Conventional Commits format', 'ensures quality-gate passes', 'prevents issue auto-closing', 'includes Co-Authored-By', 'requires user approval' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Both 'what' (detailed enforcement behaviors) and 'when' ('TRIGGER when creating commits') are present and explicit, but the 'when' clause is narrow and could name more concrete trigger phrases, so it sits just below the top anchor.	4 / 5
Trigger Term Quality	The only trigger phrase is 'TRIGGER when creating commits'; it is relevant but misses natural variations users actually say such as 'commit this', 'commit changes', 'write a commit message', or 'git commit'.	3 / 5
Distinctiveness Conflict Risk	The gitmoji + Conventional Commits niche is highly specific to commit authoring, with triggers unlikely to collide with other skills.	5 / 5
	Total	17 / 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: cteyton/packmind
Path: .claude/skills/git-commit-guidelines/SKILL.md
Commit: e198635

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