generating-conventional-commits

Execute generates conventional commit messages using AI. It analyzes code changes and suggests a commit message adhering to the conventional commits specification. Use this skill when you need help writing clear, standardized commit messages, especially a... Use when managing version control. Trigger with phrases like 'commit', 'branch', or 'git'.

Quality

41%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/packages/devops-automation-pack/skills/generating-conventional-commits/SKILL.md

Quality

Content

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

This skill is almost entirely generic boilerplate with no actionable content. It explains concepts Claude already knows, provides no executable code or commands, and contains multiple placeholder sections with no real substance. The skill would need to be fundamentally rewritten to provide concrete value—specifying the actual git commands to run, the conventional commits format rules, type selection heuristics, and example input/output pairs.

Suggestions

Replace the entire body with a concise specification: show the exact `git diff --staged` command to run, the conventional commits format (`type(scope): description`), and a decision table mapping change patterns to commit types (feat/fix/refactor/etc.).

Add concrete, copy-paste-ready examples showing actual diff output paired with the expected commit message output, rather than vague descriptions like 'Analyze the staged changes related to a new feature'.

Remove all generic boilerplate sections (Prerequisites, Instructions, Output, Error Handling, Resources) that contain only placeholder text with no skill-specific content.

Dimension	Reasoning	Score
Conciseness	The content is highly verbose, explaining obvious concepts Claude already knows (what conventional commits are, what Git staging is, how AI generates suggestions). Sections like 'How It Works', 'When to Use This Skill', 'Best Practices', 'Integration', 'Prerequisites', 'Instructions', 'Output', 'Error Handling', and 'Resources' are all filler with no actionable substance. The skill could be reduced to ~10 lines.	1 / 3
Actionability	There is no executable code, no concrete commands (not even `git diff --staged`), no actual commit message format specification, and no real instructions for how to analyze changes or construct the message. The examples are superficial illustrations rather than actionable guidance. The 'Instructions' section is completely generic boilerplate ('Invoke this skill when the trigger conditions are met').	1 / 3
Workflow Clarity	The workflow described ('Analyze Changes → Generate Suggestion → Present to User') is vague and lacks any concrete steps, commands, or validation checkpoints. There's no guidance on how to actually inspect staged changes, what heuristics to use for selecting the commit type, or how to validate the output against the conventional commits spec.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files and no bundle files to support it. Multiple sections contain generic placeholder content ('The skill produces structured output relevant to the task', 'Project documentation', 'Related skills and commands') that adds no value. There is no meaningful structure or navigation.	1 / 3
	Total	4 / 12 Passed

Description

82%

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 does a reasonable job of explaining what the skill does and when to use it, with explicit trigger terms. However, the description appears truncated ('especially a...'), some trigger terms like 'branch' and 'version control' are too broad and could cause conflicts with other git-related skills, and the specific capabilities could be more detailed.

Suggestions

Narrow the trigger terms to avoid conflicts: remove 'branch' and 'version control' which are too broad, and focus on 'commit message', 'conventional commit', 'git commit' as more distinctive triggers.

Fix the truncation and complete the description to fully convey the skill's scope, e.g., 'especially after staging changes' or similar.

Dimension	Reasoning	Score
Specificity	The description names the domain (conventional commit messages) and some actions (analyzes code changes, suggests a commit message), but doesn't list multiple concrete actions beyond that. The truncation ('especially a...') cuts off potentially useful detail.	2 / 3
Completeness	Clearly answers both 'what' (generates conventional commit messages by analyzing code changes) and 'when' (explicit 'Use when managing version control. Trigger with phrases like commit, branch, or git').	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'commit', 'branch', 'git', 'commit messages', 'version control', 'code changes'. These cover common variations of how users would request this functionality.	3 / 3
Distinctiveness Conflict Risk	While 'conventional commit messages' is fairly specific, the trigger terms 'branch' and 'git' are overly broad and could conflict with other git-related skills (e.g., branching strategies, git workflow skills). 'Version control' is also quite generic.	2 / 3
	Total	10 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 00c0702

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