From pith
Generates one-shot Conventional Commits messages for staged git changes: feat/fix/refactor types, imperative ≤50 char subjects, optional scopes and Why explanations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pith:pith-commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Conventional Commits. Subject ≤50 chars. Imperative mood.
Conventional Commits. Subject ≤50 chars. Imperative mood.
type(scope): subject
Why: [reason, only when non-obvious from the diff]
| Type | When |
|---|---|
feat | new capability |
fix | bug correction |
refactor | restructure without behavior change |
perf | measurable performance improvement |
test | add or fix tests only |
docs | documentation only |
chore | tooling, deps, config — no prod code |
ci | CI/CD pipeline changes |
build | build system changes |
Why:): only when the reason is non-obvious from subject + diff. Skip for trivial changes.! after type. feat(api)!: change response shapeGood:
fix(auth): correct token expiry unit comparison
Why: exp is Unix seconds, Date.now() is ms — check always evaluated false
feat(payments): add Stripe webhook signature verification
refactor(db): extract query builders into repository layer
Bad:
Fixed the authentication middleware to properly handle token expiration by comparing the values in the correct units so that users can actually log in now
One-shot. Does not persist.
npx claudepluginhub abhisekjha/pith --plugin pithGenerates ultra-compressed Conventional Commits messages with ≤50 char subject and body only when 'why' isn't obvious. Auto-triggers when staging changes.
Generates Conventional Commits messages from staged git changes by analyzing git diff --cached. Determines type/scope, writes imperative subjects ≤50 chars, adds body only if why not obvious. Use for commit generation or /cavemanov-commit.
Generates clear, conventional commit messages from git diffs. Useful when writing commit messages, reviewing staged changes, or preparing commits.