Git Visual Squash Summary

This skill turns a stack of commits into a curated grouped summary without touching the index, the worktree, or git history. It is the wording companion to git-visual-commits: same emoji-first language, with conventional prefixes only when the user explicitly asks for that combo, but non-mutating and optimized for the grouped summary shown beneath a PR title or in a squash-and-merge description field.

This skill is non-mutating: it inspects history and diffs, then returns grouped summary lines only. Keep inspection output in the terminal; never create repo-local scratch files to capture diffs, logs, notes, or intermediate summaries. If persistence is genuinely required, use an absolute path under the operating system's temporary directory or session storage outside the repository.

This skill has one job: produce a ready-to-paste squash-and-merge summary for the full current feature branch unless the user explicitly asked for a narrower range.

Full means every distinct surviving change from every contributor. Group related changes without losing coverage. There is no total line limit; the 72-character limit applies to each line only.

This skill answers one question: What would this branch effectively do if it were squashed into one commit now?

Start Here: The First Response Is the Summary

Invoking this skill is the request. Nothing needs confirming, because the skill mutates nothing and the scope is derivable on your own: the current branch against its base branch. A confirmation round-trip costs the user a turn and returns no information you could not have resolved yourself with git.

So the first thing to do after loading this skill is run the read-only commands in Step 1 — not compose a reply. The first thing the user sees is the finished grouped summary.