Atomic Commit Discipline

Overview

Turn completed work into small, reviewable commits with scoped validation, related task-state updates, and no unrelated files.

This skill is not a review template or ledger template. It focuses on minimal commits, exact staged paths, task-state coupling, validation, and commit messages. For shared harness terms, see ../../references/harness-patterns.md; when commit rules are absent, use references/build-when-missing.md. For delivery artifact evidence, see references/delivery-artifact-checklist.md.

When To Use

• The user asks to commit, split commits, stage exact paths, or avoid unrelated changes.
• You are preparing a commit and need to inspect git status or diffs to avoid unrelated work.
• The worktree has multiple changes and you need to decide which belong in the same logical commit.
• A tracked task is completed, changed, or invalidated and its task-state update must travel with the related commit.
• The project requires Conventional Commits or a ledger entry paired with each commit.

Inputs Needed