From e6ede7fac44f764868a9baea8b39cd503e9978ec Mon Sep 17 00:00:00 2001 From: shrimbly Date: Sat, 14 Feb 2026 22:24:54 +1300 Subject: [PATCH] docs: require per-task commits in multi-task plans Co-Authored-By: Claude Opus 4.6 --- CLAUDE.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index f5462e0d..933023f7 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -219,6 +219,7 @@ All routes in `src/app/api/`: - Never push directly to `main`, `master`, or `develop` ## Commits -- Commit frequently and atomically, if a task is complete, commit. +- Commit after each logical task or unit of work is complete. When implementing a multi-task plan, commit after finishing each task — do NOT batch all tasks into a single commit at the end. +- Each commit should be atomic and self-contained: one task = one commit. - The .planning directory is untracked, do not attempt to commit any changes to the files in this directory.