commit

Guided git commit with atomic commit analysis and conventional commit format

Quality

43%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/git-workflow/skills/commit/SKILL.md

Quality

Discovery

32%

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 identifies its domain (git commits) and hints at specific methodologies (atomic commits, conventional format), but lacks concrete action verbs and completely omits trigger guidance. Without a 'Use when...' clause, Claude cannot reliably determine when to select this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks for help writing commit messages, reviewing staged changes, or mentions conventional commits'

List concrete actions such as 'Analyzes staged changes, generates descriptive commit messages, ensures atomic commit boundaries'

Include natural trigger terms users would say: 'commit message', 'git message', 'staged changes', 'what to commit'

Dimension	Reasoning	Score
Specificity	Names the domain (git commit) and mentions two specific concepts (atomic commit analysis, conventional commit format), but doesn't list concrete actions like 'generate messages', 'analyze diffs', or 'stage changes'.	2 / 3
Completeness	Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes 'git commit' and 'conventional commit' which users might say, but misses common variations like 'commit message', 'staged changes', 'git message', or abbreviations users naturally use.	2 / 3
Distinctiveness Conflict Risk	The terms 'atomic commit analysis' and 'conventional commit format' provide some distinctiveness, but 'git commit' is generic enough to potentially overlap with other git-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

55%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is highly actionable with excellent workflow clarity and validation checkpoints, but severely undermined by extreme verbosity. The detailed interactive flow mockups and extensive example outputs bloat the content unnecessarily—Claude can generate appropriate UI flows without 200+ lines of templates. The content would benefit greatly from aggressive trimming and splitting into reference files.

Suggestions

Reduce content by 70%+ by removing verbose UI mockups and example outputs—keep only the execution instructions, validation rules, and delegation syntax

Move detailed examples and interactive flow templates to a separate EXAMPLES.md file, referenced with a single line

Consolidate the validation rules into a compact checklist format rather than prose explanations

Remove sections like 'Integration with Git Hooks' and 'Quick Commit Shortcuts' that are tangential to the core skill

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300 lines. Contains extensive UI mockups, step-by-step interactive flows, and example outputs that Claude doesn't need spelled out in such detail. The core functionality could be conveyed in under 50 lines.	1 / 3
Actionability	Provides concrete, executable guidance including specific git commands, Task tool delegation syntax, validation rules, and clear examples of commit message formats. The execution instructions are specific and actionable.	3 / 3
Workflow Clarity	Clear 8-step interactive flow with explicit validation checkpoints (atomic commit check, message validation, confirmation before commit). Error handling section covers failure cases with recovery guidance.	3 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline including detailed UI mockups, examples, and edge cases that could be split into separate reference files (e.g., EXAMPLES.md, VALIDATION.md).	1 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

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