compose-and-push-commits

To organize changes into atomic commits, the Skill groups staged and unstaged files from a messy working tree into logical units, ensuring each commit represents a single, reviewable change before pushing to the remote repository.

Cleaning up git history involves grouping changes into atomic commits, ensuring each commit is independently reviewable and revertable. The Skill manages this process and requires explicit push confirmation before sending commits to the remote.

Yes, you need a git environment to manage and clean up commits. The Skill operates within your existing git setup to organize changes and push them to the remote repository after explicit confirmation.

Yes, you can review commits before pushing because the Skill requires explicit push confirmation. It organizes your working tree changes into atomic, reviewable commits and waits for your approval before executing the remote push.

Atomic commits ensure a clean, reviewable git history by creating a single logical change per commit. This makes each commit independently reviewable and revertable, solving the problem of a messy working tree before pushing to the remote.