Git Smart Commit
by @wusuiling-if
Analyze staged git changes and generate high-quality commit messages following Conventional Commits format. Use when: (1) user asks to commit changes, (2) us...
Single file fix:
fix(auth): handle expired JWT tokens in refresh flow
Multi-file feature:
feat(api): add pagination support to list endpointsImplement cursor-based pagination for /users, /posts, and /comments.
Default page size is 20, max 100.
Breaking change:
feat(config)!: migrate from YAML to TOML configurationBREAKING CHANGE: config.yaml is no longer supported.
Run migrate-config to convert existing configs.
Chore:
chore(deps): bump express from 4.18.2 to 4.19.0
The user may specify preferences:
--no-body: Skip the body, subject only--scope : Force a specific scope--type : Force a specific type--amend: Amend the previous commit instead--dry-run: Generate message without committingfeat, fix, refactor, docs, chore, test, style, perf, ci, buildauth, api, ui, db). Omit if changes span too many areas.! after type/scope and BREAKING CHANGE: footer.git add -p.Type Selection Guide
| Signal | Type |
|--------|------|
| New feature, new endpoint, new UI element | feat |
| Bug fix, error correction, patch | fix |
| Code restructure, no behavior change | refactor |
| Comments, README, docs, JSDoc | docs |
| Dependencies, configs, tooling | chore |
| Test files added/modified | test |
| Formatting, whitespace, linting | style |
| Performance improvement | perf |
| CI/CD pipeline changes | ci |
| Build system, compilation | build |
Quality Checklist
Before presenting the message, verify:
git log --oneline can understand the change)clawhub install git-smart-commit