661 B
661 B
Commits must be atomic — one task = one commit
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