skills.rest
lonestar62
lonestar62COMMUNITY
Explore all skills by this author →
GitHub

merge-pr

Squash-merge verified GitHub pull requests with co-author attribution.

Updated Aug 23, 2026
Search Tags:#automation#git#pull request#github#merge#squash
One-click install
npx skills add https://github.com/lonestar62/OpenclawAI --skill merge-pr-lonestar62
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/lonestar62/OpenclawAI/tree/main/.openclaw-src/.agents/archive/merge-pr-v1
Command: npx skills add https://github.com/lonestar62/OpenclawAI --skill merge-pr-lonestar62

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of merging prepared GitHub Pull Requests (PRs) using a squash merge strategy, ensuring a clean and traceable commit history.

Core Features & Use Cases

  • Squash Merging: Merges PRs by squashing all commits into a single commit on the target branch.
  • Automated Cleanup: Removes the feature branch and worktree after a successful merge.
  • Verification: Ensures PR checks are passing and the PR head commit hasn't changed since preparation.
  • Use Case: After a PR has been reviewed and prepared for merging, use this Skill to finalize the merge without manual intervention, maintaining repository integrity.

Quick Start

Use the merge-pr skill to merge pull request number 123.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I automate a squash merge for a GitHub pull request?▼

Squash merging a GitHub pull request is automated by verifying readiness, confirming the head commit matches the prepared state, checking all required statuses are green, and then executing the squash merge with co-author attribution.

What happens to the feature branch and worktree after a successful squash merge?▼

After a successful squash merge, automated cleanup removes the associated feature branch and worktree to maintain repository cleanliness and prevent stale local environments from accumulating.

Can I merge a draft pull request using squash automation?▼

Draft pull requests cannot be squash merged using this automation because it verifies the PR is not a draft and requires all mandatory checks to pass before proceeding with the merge.

Why does my pull request squash merge fail when the head commit changes?▼

Squash merge execution fails when the head commit changes because the automation verifies that the current pull request head commit exactly matches the prepared state before allowing the merge to proceed.

Does the squash merge automation include co-author attribution in the commit?▼

Squash merge automation includes explicit co-author attribution in the final commit, ensuring traceability of contributors while maintaining a clean, single-commit history on the target branch.

Related Skills

Explore More Software Engineering Skills→
drillandrillan
1

merge-pr

Wait for CI checks and merge GitHub pull requests with a chosen strategy.

Community
Advanced
cowwoccowwoc
4

git-merge-linear

Merge a task branch into main with a linear history and verification.

Community
Intermediate
HahyeonJeonHahyeonJeon

_git

Coordinate Git/GitHub workflows with isolated worktrees and central orchestrator control.

Community
Advanced
kubuszokkubuszok
6

verified-merge

Merges GitHub pull requests while preserving users' verified commit signatures.

Official
Advanced