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 after making code changes and preparing to commit. Trigger with terms like "create commit", "generate commit message", or "write commit".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-conventional-commits64
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Conventional commit type and format
fix: prefix used
66%
100%
Colon-space separator
80%
100%
Lowercase type prefix
100%
100%
Specific description
100%
100%
No period at end
100%
100%
Imperative mood
100%
100%
Single subject line
100%
100%
Output file created
100%
100%
Diff-based content
100%
100%
Without context: $0.0863 · 25s · 8 turns · 9 in / 1,157 out tokens
With context: $0.2743 · 52s · 18 turns · 51 in / 2,706 out tokens
Multi-change type categorization
feat: for new endpoint
100%
100%
docs: for README change
100%
100%
chore: or build: for dependency bump
100%
100%
Separate commits per change
100%
100%
Format consistency
100%
100%
Specific descriptions
100%
100%
Lowercase type prefixes
100%
100%
Output file created
100%
100%
No period at end of subjects
100%
100%
Imperative verb in description
100%
100%
Without context: $0.1186 · 29s · 8 turns · 8 in / 1,465 out tokens
With context: $0.3432 · 1m 15s · 21 turns · 55 in / 3,712 out tokens
Commit message review and customization
feat: type prefix
100%
100%
type: description format
100%
100%
Lowercase type
100%
100%
Subject line concise
100%
0%
Body included
100%
100%
Blank line before body
100%
100%
Body explains motivation
66%
33%
Specific subject line
100%
100%
No period ending subject
100%
100%
Output file written
100%
100%
Without context: $0.1437 · 42s · 12 turns · 13 in / 1,792 out tokens
With context: $0.3225 · 1m 19s · 16 turns · 17 in / 3,936 out tokens
Non-feat/fix commit type selection
refactor: type used
100%
100%
type: description format
100%
100%
Lowercase type prefix
100%
100%
Subject line length
100%
100%
No period at end
100%
100%
Imperative mood
100%
100%
References restructuring
100%
100%
Does NOT use feat or fix
100%
100%
References transaction processor
100%
100%
Output file written
100%
100%
Without context: $0.0943 · 28s · 8 turns · 9 in / 1,170 out tokens
With context: $0.3838 · 1m 18s · 23 turns · 22 in / 4,199 out tokens
Breaking change commit notation
Breaking change signaled
100%
100%
Conventional type prefix
100%
100%
type: description format
100%
100%
Lowercase type prefix
100%
100%
Subject line length
100%
100%
No period at end
100%
100%
Imperative mood
100%
100%
References v1 endpoint
100%
100%
BREAKING CHANGE footer format
100%
100%
Output file written
100%
100%
Without context: $0.1049 · 25s · 9 turns · 8 in / 1,202 out tokens
With context: $0.2653 · 58s · 17 turns · 49 in / 3,087 out tokens
Message customization and context
feat: type prefix
100%
0%
type: description format
100%
100%
Lowercase type prefix
100%
100%
Subject line length
0%
0%
No period at end
100%
100%
Body is present
100%
100%
Blank line before body
100%
100%
Body provides motivation
100%
100%
Commit file written
100%
100%
Review notes written
100%
100%
Without context: $0.1637 · 42s · 11 turns · 12 in / 2,118 out tokens
With context: $0.3657 · 1m 17s · 25 turns · 58 in / 3,883 out tokens
Commit scope notation
Scope included
100%
100%
Auth scope value
100%
100%
feat: type prefix
100%
100%
type(scope): format
100%
100%
Lowercase type and scope
100%
100%
Subject line length
100%
100%
No period at end
100%
100%
Imperative mood
100%
100%
References OAuth or token validation
100%
100%
Output file written
100%
100%
Without context: $0.1047 · 28s · 9 turns · 10 in / 1,415 out tokens
With context: $0.3815 · 1m 23s · 22 turns · 23 in / 4,670 out tokens
perf commit type selection
perf: type used
100%
100%
Does NOT use feat or fix
100%
100%
type: description format
100%
100%
Lowercase type prefix
100%
100%
Subject line length
0%
100%
No period at end
100%
100%
Imperative mood
100%
100%
References query or cache
100%
100%
Output file written
100%
100%
Without context: $0.1536 · 46s · 10 turns · 11 in / 2,723 out tokens
With context: $0.3640 · 1m 36s · 24 turns · 25 in / 4,762 out tokens
Issue reference in commit footer
Issue reference in footer
100%
100%
Footer separated by blank line
100%
100%
fix: type prefix
100%
100%
type: description format
100%
100%
Lowercase type prefix
100%
100%
Subject line length
100%
100%
No period at end of subject
100%
100%
Imperative mood
100%
100%
References filename or upload
100%
100%
Output file written
100%
100%
Without context: $0.1200 · 27s · 9 turns · 10 in / 1,191 out tokens
With context: $0.3962 · 1m 31s · 21 turns · 57 in / 4,689 out tokens
Table of Contents
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.