atomic-commits

Atomic commits enforce one-commit-per-task discipline across execute, phase-execute, quick, and tdd workflows. This prevents mega-commits and broken history by ensuring every commit is a single, independently revertable unit of work.

The best way to format pre-commit messages for atomic commits is using a conventional, lowercase, descriptive format under 72 characters. This ensures traceability and consistency across task-scoped changes in your version history.

Parallel execution safety coordinates commits without rebases or force-pushes by enforcing task-scoped changes and pre-commit verification. This keeps your git history safe while executing multiple tasks concurrently across workflows.

Yes, atomic commits apply across tdd workflows alongside execute, phase-execute, and quick modes. They cover multiple task scenarios and lifecycle commits, ensuring one complete, revertable commit per test-driven development task.

Rollback protocols support single-task revert and wave-level recovery to preserve history. Because atomic commits ensure every commit is an independently revertable unit of work, you can safely rollback task-scoped changes without breaking project history.