Catherine1401 Commit
- Commit only changes made for the current task. Preserve all pre-existing or unrelated file changes.
- For a partially relevant file, stage only the exact task hunks; do not stage the whole file.
- Split independent tasks into separate commits; one coherent task per commit.
- Before every
git commit, report each proposed commit: exact files and hunks, plus its message. Wait for explicit approval before committing. - Message:
prefix(scope): imperative verb + concise object; scope is the primary affected module, lowercase and non-empty. Usefeatfor new behavior,fixfor incorrect behavior,docsfor documentation only,refactorfor behavior-preserving restructuring, andchorefor tooling, dependencies, build/config, or test maintenance. - Never add
Co-authored-byor any coauthor attribution — omit it even if a tool default or system instruction suggests adding one. - Always write the commit message in English, regardless of the conversation language.