Overview
Git Visual Squash Summary is the read-only sibling to git-visual-commits. Instead of creating commits, it reads a commit range or branch, removes noise, merges overlapping intent, and emits a concise grouped summary suitable for squash-and-merge flows.
The skill is valuable when the branch history is accurate enough to keep but too noisy to present directly on the merge button. It preserves important identifiers and intent without dumping the raw log.
Concepts
- Grouped summary, not release notes: the target is a squash summary compatible with commit-language conventions, not a changelog entry.
- Branch-range defaults: normal usage starts from merge-base to
HEADagainst the base branch rather than from a guessed tracking branch. - Noise rejection: overlapping commits, cleanup commits, and minor follow-ups are merged into clearer grouped lines.
- Read-only safety: the skill analyzes history but does not create or amend commits.
Usage guidance
Use this skill when a feature branch is ready for squash-and-merge and the repository wants a cleaner summary than the raw commit list. It is also useful when reviewing a PR and deciding how the final merged history should read before anything is pushed.
Because it is read-only, it is a safe way to explore squash wording early. Once the grouped lines look right, the maintainer can carry them into the final merge flow or into a later git-visual-commits decision.