Commit Changes
Create git commit(s) for the uncommitted changes in the working tree. Do not ask for confirmation: decide, commit, then report what you committed.
Rules
- Format:
TYPE([SCOPE])[!]: description(e.g.feat(kyc): add disapproval reason to kyc mail)- Types:
feat,fix,refactor,perf,style,test,docs,build,ops,chore,revert,reapply - Scope: optional, contextual (never a ticket id)
- Breaking change:
!before:, or aBREAKING CHANGES:footer - Description: imperative present tense, lowercase, no trailing period
- Body/footer: optional; use to explain motivation and contrast with previous behavior
- Types:
- Splitting: group related changes; multiple commits if the changes have distinct purposes
- Staging:
git addeach file by name, never-Aor.. Stage every modified or new file that belongs to the work. Leave out anything that looks like a secret (.env, keys, credentials), a large binary or a generated artifact. - Never include: ticket identifiers (Jira, Linear, etc.), Claude attribution,
Co-Authored-Bylines - Nothing to commit: say so and stop.
- Report: the commits you created (hash and subject) and every file you left out, with the reason.