Atomic Commits

Core Question

How should the selected change scope be split into minimal coherent commits without staging unrelated work, overwriting user choices, or hiding risky behavior?

When To Use

Use this skill when the user asks to:

• organize staged changes into atomic commits,
• split explicitly included changes into multiple commits,
• propose grouping for unstaged or untracked changes without staging by default,
• stage exact hunks or files only after explicit file/hunk confirmation,
• create several local commits from a large change when the source scope is explicit.

When Not To Use

Do not use this skill for message-only work, branch synchronization, conflict resolution, recovery, versioning, release notes, or tags.