Commit Message Formatter - Auto-activating skill for DevOps Basics. Triggers on: commit message formatter, commit message formatter Part of the DevOps Basics skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill commit-message-formatter34
Quality
3%
Does it follow best practices?
Impact
86%
0.91xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/commit-message-formatter/SKILL.mdCommit message validation hook
Conventional Commits type
100%
100%
Scope support
100%
100%
Subject line length check
100%
50%
Non-empty subject
100%
100%
Breaking change support
50%
0%
Executable hook file
70%
30%
Clear error output
100%
70%
Exit codes
100%
100%
Production-ready script
100%
100%
Installation documentation
100%
100%
Without context: $0.3309 · 3m 35s · 18 turns · 19 in / 5,369 out tokens
With context: $0.4202 · 3m 44s · 25 turns · 98 in / 5,074 out tokens
Commit message formatting and best practices
Type prefix applied
100%
0%
Imperative mood
91%
100%
Subject line under 72 chars
70%
100%
No trailing period
100%
100%
Body separation
100%
100%
Body wrapping
100%
100%
Rationale in body
90%
50%
Step-by-step explanation
100%
100%
All inputs processed
100%
100%
Output file produced
100%
100%
Without context: $0.1785 · 1m 55s · 13 turns · 14 in / 2,874 out tokens
With context: $0.3680 · 3m 30s · 22 turns · 21 in / 4,792 out tokens
CI/CD commit linting pipeline setup
CI config file present
100%
100%
Commit lint job defined
100%
100%
Conventional Commits enforcement
100%
100%
Subject line length rule
50%
100%
Fails pipeline on violation
100%
100%
Validation against standards
100%
100%
Production-ready config
100%
100%
PR/MR range linting
100%
100%
Error message output
100%
100%
Usage documentation
100%
100%
Without context: $0.3842 · 3m 36s · 21 turns · 22 in / 5,568 out tokens
With context: $0.4563 · 3m 44s · 25 turns · 24 in / 6,125 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.