When changing code, update commit.txt in the repo root with the commit message. Do NOT run git commands to stage or commit — the user handles that manually.
- Use Conventional Commits format directly (not markdown, not a description of changes).
- First line:
PROJ-123: <type>(<optional scope>): <short summary>(max 72 chars), PROJ-123 is a jira issue number (only if known, otherwise skip) - Blank line, then optional body explaining why (wrap at ~80 chars).
- The file is gitignored.
- If
commit.txtalready exists, the user has not committed yet — read it first, then merge/summarize the new changes together with the existing message so the file always covers all uncommitted changes since the last git commit. - If
commit.txtdoes not exist, create it fresh.
- Types: feat, fix, refactor, chore, docs, perf, test
- Use imperative mood: "add", "fix", "remove".
- Do not mention specific filenames.
commit.txtmust describe all current changes since the last git commit.- Every commit must reference an issue
- Body is optional but when present:
- Explain why, not what.
- Wrap lines at ~80 chars.