git-squash

Plan and execute commit squashes for PRs via interactive rebase after approval.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cuozg/oh-my-unity --skill git-squash-cuozg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-squash
Source: https://github.com/cuozg/oh-my-unity/tree/main/skills/git-squash
Command: npx skills add https://github.com/cuozg/oh-my-unity --skill git-squash-cuozg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Squash commits for a PR — analyze, group, plan, get approval, execute — use for 'squash commits', 'squash for PR', 'clean up commits', 'combine commits'

Core Features & Use Cases

  • Analyze a branch's commit history and identify logical groups of changes.
  • Group related commits into a squash plan and prepare an approval-ready proposal.
  • Apply the squash via an interactive rebase after explicit user consent.

Quick Start

Approve the squash plan to execute the interactive rebase on your feature branch.

Frequently Asked Questions about git-squash

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I squash commits for a pull request?

To squash commits for a pull request, this Skill analyzes your branch history, groups related commits into a plan, and executes an interactive rebase after you approve the proposed changes to consolidate your work.

What is the best way to clean up commit history before merging?

The best way to clean up commit history before merging is to use a deterministic workflow that analyzes commits, groups them by concern, proposes a squash plan, and applies an interactive rebase for a clean history.

Can I group related commits into a squash plan automatically?

Yes, you can group related commits automatically by analyzing the branch history to identify logical groups of changes, which generates an approval-ready squash plan before any interactive rebase is executed.

Does squashing commits require approval before applying changes?

Yes, squashing commits requires explicit user approval before applying changes, ensuring you review the proposed commit groupings and squash messages before the interactive rebase modifies your feature branch.

How does an interactive rebase handle combining commits?

An interactive rebase handles combining commits by applying an approved squash plan to your feature branch, consolidating grouped changes into a clean history with proposed messages before the final merge.