Create well-structured git commits with meaningful messages.
Creates well-structured git commits with meaningful messages following conventional commit format.
/plugin marketplace add onmyway133/claude-code-plugins/plugin install onmyway133-super-plugins-super@onmyway133/claude-code-pluginsCreate well-structured git commits with meaningful messages.
/commit [type]
Arguments:
type - Optional: feat, fix, refactor, docs, test, choreRun these commands to understand what changed:
git status
git diff --staged
git diff
If nothing is staged, ask whether to stage all changes or specific files.
Determine the primary change type:
| Type | When to Use |
|---|---|
feat | New feature or capability |
fix | Bug fix or correction |
refactor | Code restructuring (no behavior change) |
docs | Documentation only |
test | Adding or updating tests |
chore | Build, tooling, dependencies |
Follow this format:
<type>: <concise summary in imperative mood>
<optional body explaining what and why>
<optional footer with references>
Rules:
Good Examples:
feat: add user authentication with JWT tokens
Implement login/logout flow with secure token storage.
Tokens expire after 24 hours and refresh automatically.
Closes #123
fix: prevent crash when network unavailable
Handle nil response gracefully instead of force unwrapping.
Bad Examples:
fixed stuff # Too vague
WIP # Not descriptive
Updated files # Says nothing useful
Stage files if needed and create the commit:
git add <files>
git commit -m "<message>"
Show the result with git log -1.