merge

Squash-merge approved pull requests and delete remote branches via gh CLI.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/saitoco/wholework --skill merge-saitoco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/saitoco/wholework/tree/main/skills/merge
Command: npx skills add https://github.com/saitoco/wholework --skill merge-saitoco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates squash-merging a pull request and cleaning up the remote branch after merge, reducing manual merge toil and drift in collaborative repos.

Core Features & Use Cases

  • Squash-merge PRs via GitHub CLI with automatic branch deletion after merge.
  • Automatically handles simple conflicts and guides resolution for complex cases.
  • Applies to review-approved, CI-passing PRs and updates related issues or messaging post-merge.

Quick Start

Run a merge command against a PR to squash-merge it, delete the merged branch, and trigger follow-up steps.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I automate squash-merging a pull request on GitHub?▼

Automate squash-merging a pull request by running a merge command that uses gh CLI and git to squash-merge the PR, delete the remote branch, and update post-merge state. This works on review-approved, CI-passing PRs to reduce manual merge toil.

Can I automatically resolve git conflicts when merging a pull request?▼

You can automatically resolve git conflicts when merging a pull request for simple conflict cases. For complex conflicts, the automation prompts for user decisions to guide the resolution process safely.

Does automated PR merge delete the remote branch afterwards?▼

Automated PR merge deletes the remote branch automatically after the squash-merge completes. This branch cleanup prevents drift in collaborative repos and is handled via GitHub CLI tooling.

What's the best way to handle post-merge state after squash-merging a PR?▼

The best way to handle post-merge state is to use an automated squash-merge process that updates related issue references and messaging after the PR merges and the remote branch is deleted.

When should I not use automated squash-merge for pull requests?▼

You should not use automated squash-merge for pull requests that lack review approval or have failing CI checks. The Skill enforces safe push and applies only to approved, passing PRs.

Do I need GitHub CLI installed to automate squash-merging pull requests?▼

You need GitHub CLI and git installed to automate squash-merging pull requests. The Skill implements its merge steps via Bash tooling using these dependencies to enforce safe push and handle branch deletion.