commit-work

Create logical, well-described git commits with staged review and Conventional Commits formatting. Make commits that are easy to review and safe to ship: Provide: - Guides you through inspecting changes, deciding commit boundaries, and staging only intended modifications using patch mode when needed - Enforces Conventional Commits format (type, scope, subject, body, footer) with clear separation of what changed and why - Includes a pre-commit checklist covering secrets detection, accidental debug code, and unrelated formatting to catch issues before shipping - Splits mixed changes across files or within single files by feature, backend/frontend, logic/tests, and dependency updates to keep commits logically scoped - only intended changes are included - commits are logically scoped (split when needed) - commit messages describe what changed and why - Single commit or multiple commits? (If unsure: default to multiple small commits when there are unrelated changes.) - Commit style: Conventional Commits are required. - Any rules: max subject length, required scopes. - Inspect the working tree before staging - git status - git diff (unstaged) - If many changes: git diff --stat - Decide commit boundaries (split if needed) - Split by: feature vs refactor, backend vs frontend, formatting vs logic, tests vs prod code, dependency bumps vs behavior changes. - If changes are mixed in one...