squash-merge

To squash merge a pull request, this skill fetches PR details, drafts a commit message following project standards, and executes the merge using the GitHub CLI command gh pr merge --squash after user approval.

Formatting commit messages for a squash merge involves generating a subject line and body with proper wrapping in imperative mood, which this skill drafts automatically before presenting it for your review and approval.

Yes, you can use the GitHub CLI to squash merge a PR without local Git complexity by leveraging the gh pr merge --squash command server-side, which this skill automates while drafting the commit message.

Squash merging a PR requires explicit user approval before executing the merge, operating in a two-phase workflow that separates commit message drafting from the actual GitHub API merge execution.

You should choose a squash merge over a rebase merge when you want to consolidate a pull request's history into a single, clean commit, as this skill is specifically designed for squash merge scenarios.

Your squash merge commit message needs to follow project standards to maintain a clean and consistent Git history, which this skill enforces by drafting the subject line and body according to specific formatting rules.