commit-conventions
Use when the user asks for a commit message or wants help summarizing staged changes, e.g. "write a commit" or "git commit message". Reads the staged diff, picks the Conventional Commits type (feat, fix, refactor, docs, test, perf, chore), and writes an imperative subject of at most 72 characters, adding a body only for breaking changes, migrations or security fixes.
75
94%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The canonical home for this skill is commit-conventions in chandler767/WorkJournal
No evaluations available
This skill hasn't been evaluated yet
tessl scenario generatetessl eval runIs 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.