From developer
Generates descriptive commit messages following conventional commits format by analyzing git diffs. Useful when writing commit messages or reviewing staged changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/developer:git-commit-helperThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyse staged changes and generate a commit message:
Analyse staged changes and generate a commit message:
git diff --staged
Follow conventional commits format:
<type>(<scope>): <description>
[optional body]
[optional footer]
feat(auth): add JWT authentication
Implement JWT-based authentication system with:
- Login endpoint with token generation
- Token validation middleware
- Refresh token support
For more examples (bugfix, refactor, multi-file, breaking changes, scopes), see
references/examples.md.
DO:
DON'T:
git diff --stagedFor git commands (analysing diffs, interactive staging, amending commits), see
references/git-commands.md.
references/examples.md - Detailed commit message examples (feature, bugfix, refactor, multi-file, breaking changes, scope examples)references/git-commands.md - Git commands for analysing changes, interactive staging, and amending commitsnpx claudepluginhub henkisdabro/wookstar-claude-plugins --plugin developerGenerates clear, conventional commit messages from git diffs. Useful when writing commit messages, reviewing staged changes, or preparing commits.
Generates conventional git commit messages by analyzing staged changes, categorizing types like feat/fix, adding scopes, and matching project history style.
Generates conventional commit messages from staged changes by analyzing git diff and status. Helps users write structured, meaningful commits.