atomic-commitslisted

# 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. Route to: - `conventional-commits` for commit message generation or validation only. - `branch-workflow` for branch creation, switching, sync, upstream, push, or remote refs. - `resolve-conflicts` when the index has unmerged paths or conflict markers. - `undo-recover` for reset, restore, abort, reflog, stash, broad unstage, or recovery work. - `version-bump`, `changelog-maintenance`, `release-notes`, or `tag-release` for release workflows. ## Required Evidence Before action, inspect or establish: - `git status --short --branch`, - staged file list and staged diff, - unstaged and untracked file list as excluded evidence by default, - generated files, lockfiles, and documentation changes, - project instructions and commit convention