Commit with Pre-checks
Steps
- •Run
bun lintto check for ESLint issues - •Run
bun run buildto verify TypeScript compiles and Vite builds - •Run
bun tauri buildto verify the full Tauri app builds - •If any check fails, stop and report the error
- •If all checks pass, show:
- •Files to commit with status and change summary
- •Proposed commit message following the format in CLAUDE.md
- •Wait for explicit user approval before committing
Rules
- •NEVER auto-commit or push without explicit approval
- •NEVER push to remote unless explicitly asked
Commit Message Format
code
type(scope): subject line (<72 chars) Context paragraph explaining WHY this change is needed, what was broken, or what motivated the change. - Bullet points describing WHAT changed - One bullet per logical change
- •Types:
feat,fix,docs,style,refactor,test,chore - •Scope is optional (e.g.,
tauri,dnd,hooks,components) - •Subject: lowercase, imperative mood, no period
- •Body: blank line after subject, wrap at 72 chars
- •Context paragraph explains the problem or motivation
- •Bullet list covers the concrete changes