flow-primitive-commit

Task-scoped git commits are created by selectively staging only the files relevant to your active task, ensuring focused changes. This avoids generic staging and produces a clear, present-tense commit message for better traceability.

Present-tense commit messages are enforced to keep version control history clear and actionable. They concisely summarize what the commit does, improving traceability and making code reviews easier to follow across task-scoped changes.

The best way to isolate changes by task is to explicitly stage only the relevant files for that specific task, then verify the post-commit state. This prevents unrelated noise from polluting the review and maintains a clean project history.

No, you cannot amend or rewrite history unless explicitly requested. The workflow guards against history rewriting to maintain a verifiable and safe post-commit state, ensuring that task-scoped commits remain traceable.

You avoid generic git add by enforcing explicit file staging, where you selectively stage only the files relevant to your current task. This ensures commits stay scoped to a single task and reduces noise in your version control history.