Consolidate commits on the current branch into a single Conventional Commits message.
npx skills add https://github.com/KosmoCHE/claude-plugins --skill squash-kosmoche
Please help me install this Agent Skill. Skill: squash Source: https://github.com/KosmoCHE/claude-plugins/tree/main/git-command/skills/squash Command: npx skills add https://github.com/KosmoCHE/claude-plugins --skill squash-kosmoche
Squashing multiple commits on the current branch into a single commit helps maintain a tidy project history, simplifies code reviews, and makes reverts easier.
Squash the last N commits on the current branch into a single conventional commit.
High-intent search queries and answers about installing and using this skill.
To squash commits before merging, the process calculates the merge-base with your main branch, performs a soft reset to that point, and replays all branch changes into a single commit. This keeps your project history tidy and simplifies code reviews.
Consolidating multiple commits into one conventional commit is done by soft resetting to the merge-base and creating a new commit message formatted to the Conventional Commits specification, ensuring a clean and consistent project history.
Yes, you can limit the squash scope to the last N commits. By providing an optional scope control parameter, the commit consolidation restricts its range, allowing you to squash exactly the desired number of recent commits.
Squashing with a soft reset preserves your working directory changes because it moves the branch pointer to the merge-base without altering your files. All changes are then replayed into a single new commit, ensuring no work is lost.
You should squash feature commits before merging to main because it helps maintain a tidy project history, simplifies code reviews by presenting changes coherently, and makes reverts easier if a bug is introduced.
MartinoPoloMerge a target branch into the current branch with Git safety checks.
WesleyMFrederickSquashes Git feature-branch history into a single commit when merging to main.
samberStandardize Git commit messages and branch naming using Conventional Commits v1.0.0 rules.
maggitPlan and execute non-interactive git rebase operations with safety checks.
