Stats
Actions
Tags
From commit-message-guide
Guide for creating well-structured conventional commits. TRIGGER when: about to run `git commit`, user asks to commit or save changes to git, or drafting/reviewing a commit message. Use for single logical changes. Enforces conventional commit format, forbids AI attribution and Co-Authored-By trailers.
How this skill is triggered — by the user, by Claude, or both
Slash command
/commit-message-guide:commit-message-guideThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Only include a body when the title and file changes alone cannot reasonably convey the reason for the commit.**
Only include a body when the title and file changes alone cannot reasonably convey the reason for the commit.
Never include:
WIP — no formatting required, may have failing tests:
WIP: debugging race condition in scheduler
FIXUP — created with git commit --fixup=<hash> for automatic squashing:
fixup! feat(api): add support for webhook callbacks
WIP and FIXUP commits skip all other requirements.
If the work spans multiple concerns, use purposeful-commits first to structure the commits, then apply this guide to each individual message.
git status for untracked files among those being staged. If any are untracked, the commit introduces something new — use feat (or docs/test/etc.), not fix. A fix presupposes something existed and was broken.Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub beflagrant/skills-marketplace --plugin commit-message-guide