Git Squash

To squash multiple git commits into one, this Skill non-interactively combines recent commits into a single, cleaner commit. It prepares your project history for pull requests by merging smaller commits without requiring manual editor intervention.

Cleaning up WIP and fix typo commits in your Git history is done by squashing them into a single, descriptive commit. This creates a more meaningful and organized version control record for your project.

You can squash all commits since a specific branch non-interactively. This Skill supports flexible targeting to combine commits since a given branch, bypassing the need for manual interactive rebase editor sessions.

Previewing changes and generating a combined commit message when squashing commits is supported directly. The Skill offers options to preview the squashed changes and automatically generate a combined message for the new commit.

Squashing a specific number of recent commits works effectively for organizing GitHub version control. You can target an exact number of recent commits to merge, ensuring a cleaner project history before submission.

You should avoid squashing your git commit history when you need to preserve the detailed, incremental context of individual commits. Squashing permanently combines these separate commits into a single record, losing granular tracking.