StaffinityAI Conventional commit
A standalone, command-style skill — no MCP server involved. It shows the pattern
of a skill you trigger explicitly with /conventional-commit rather than one
Claude picks on its own (disable-model-invocation: true).
Steps
Inspect what is staged: run
git diff --cached(andgit statusfor context).- If nothing is staged, tell the user to
git addfirst and stop.
- If nothing is staged, tell the user to
Decide the type from the change:
feat,fix,docs,refactor,test,chore,perf,build,ci, orstyle.Pick an optional scope (the affected area, e.g.
mcp_advanced).Write the message:
<type>(<scope>): <imperative summary, <=50 chars, no trailing period> <optional body: why the change was made, wrapped at ~72 cols>Add a
BREAKING CHANGE:footer if the change is incompatible.Present the message in a fenced block. Do not run
git commitunless the user explicitly asks you to.
Example
feat(mcp_advanced): add search_notes tool
Lets clients find notes by substring instead of only listing all of
them, mirroring the create/read pair already exposed.