Private
Public Access
1.0 KiB
1.0 KiB
atomic_per_task_commits — v1
Why this iteration: Lifted verbatim from conductor/workflow.md §"Standard Task Workflow" step 9 (line 112) + AGENTS.md "Critical Anti-Patterns" (line 55). This is the baseline encoding — the imperative-bullet style currently in production.
Future variants will test alternative encodings (rationale-first, before/after) against this baseline.
Source: conductor/workflow.md:112 + AGENTS.md:55
From conductor/workflow.md §"Standard Task Workflow" step 9:
- CRITICAL - ATOMIC PER-TASK COMMITS: You MUST commit your changes immediately after completing and verifying a single task. Do NOT move on to the next task in the plan without committing the current one. This ensures precise tracking and safe rollback points.
- Stage all code changes related to the task.
- Propose a clear, concise commit message e.g,
feat(ui): Create basic HTML structure for calculator. - Perform the commit.
From AGENTS.md "Critical Anti-Patterns":
- Do not batch commits - commit per-task for atomic rollback