Stats
Actions
Tags
From workflow-tools
Guide for creating well-structured conventional commits. Use when creating git commits, drafting commit messages, or reviewing commit message quality.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workflow-tools:commit-message-guideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill ensures commit messages follow conventional commit format with command tense and concise, meaningful content.
This skill ensures commit messages follow conventional commit format with command tense and concise, meaningful content.
<type>(<scope>): <subject>
[optional body]
[optional footer]
Use one of these conventional commit types:
feat: New featurefix: Bug fixrefactor: Code change that neither fixes a bug nor adds a featureperf: Performance improvementstyle: Code style changes (formatting, missing semicolons, etc.)test: Adding or updating testsdocs: Documentation changesbuild: Build system or dependency changesci: CI/CD configuration changeschore: Other changes that don't modify src or test filesThe scope provides context about what area of the codebase is affected. Use appropriate scope for the module/component being changed, e.g.:
api, auth, db, ui, config, cli, coreExamples:
feat(api): add support for batch operationsfix(auth): handle expired token refreshrefactor(db): simplify query builder logicBad examples:
feat(api): Added support for batch operations (wrong tense)Fixed a bug in auth (missing type/scope, wrong tense)Only include a body when the title and file changes alone cannot reasonably convey the reason for the commit.
feat(api): add support for webhook callbacks
Implements webhook delivery for event notifications.
Uses a retry queue with exponential backoff to handle
transient failures without losing events.
refactor(db): restructure query parser
Reorganizes query parsing to use a table-driven approach
instead of a large switch statement. This makes it easier
to add new query types and reduces code duplication.
fix(auth): correct token expiry handling
Changes 3 files with 45 additions and 12 deletions.
All tests pass.
This fix took longer than expected, about 2 days.
WIP: debugging race condition in scheduler
These don't need to follow strict formatting and may have failing tests.
fixup! feat(api): add support for webhook callbacks
Created with git commit --fixup=<commit-hash> for automatic squashing during rebase.
Before creating a commit, verify:
Exception: WIP or FIXUP commits may skip these requirements.
feat(ui): add variable binding display command
The title clearly describes what was added. The diff will show the implementation.
perf(core): optimize instruction dispatch loop
Replace computed goto with direct threaded code. This
reduces dispatch overhead by eliminating one memory
indirection per instruction. Trade-off is slightly
larger binary size due to code duplication.
fix(db): handle empty name table
Modified src/db.zig to add a check for empty tables.
Updated tests to cover this edge case. All 47 tests pass.
This was a quick fix, only took about an hour.
None of this information adds value.
npx claudepluginhub code0100fun/botfiles --plugin workflow-toolsGenerates concise conventional git commit messages prioritizing 'why' over 'what', with proper types, scopes, imperative mood, and atomic structure. Use when writing commits or learning best practices.
Git commit message conventions: structure, formatting, scoping, body content, breaking changes, trailers. Invoke whenever task involves any interaction with commit messages — writing, reviewing, validating, or understanding message format.
Guides Git commit messages to follow Conventional Commits v1.0.0 spec, covering types (feat, fix, refactor, etc.), scopes, structure, body, footers, and examples. Use for code commits and PR reviews.