Write Git commit messages following the Conventional Commits specification.
npx skills add https://github.com/davidsneighbour/clerkwork --skill commit-davidsneighbour
Please help me install this Agent Skill. Skill: commit Source: https://github.com/davidsneighbour/clerkwork/tree/main/skills/commit Command: npx skills add https://github.com/davidsneighbour/clerkwork --skill commit-davidsneighbour
High-intent search queries and answers about installing and using this skill.
Use the format type(scope): description, where type is one of feat, fix, docs, style, refactor, perf, test, chore, build, ci, or revert. Write the description in imperative present tense, lowercase, without a trailing period, and keep it under 72 characters.
Add an exclamation mark after the type or scope, like feat(api)!: remove deprecated endpoint, or include a BREAKING CHANGE: footer in the commit body explaining what changed and any migration steps required.
The standard types are feat, fix, docs, style, refactor, perf, test, chore, build, ci, and revert. Use chore only when no more specific type applies to the change being committed.
Yes, run git status and git diff or git diff --cached before drafting the message. Never guess the message from the file list alone, since the actual changes determine the correct type, scope, and description.
Include a body for complex changes, non-obvious design decisions, or migration instructions, explaining why rather than what. Use footers for breaking changes, issue references like Closes #123, and co-author attribution.
jvm-skillsGroup unstaged Git changes into logical commits with concise messages.
p-o-ke-naeGenerate changelogs from commits, pull requests, and releases.
TalonT-OrgAnalyze GitHub issues for mixed concerns and create labeled sub-issues with cross-references.
PVPhaGenerate conventional commit messages with optional Gitmojis, scopes, bodies, and footers.
