merge-pr

Squash merge GitHub pull requests with safety checks and branch cleanup.

55|6|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/NJX-njx/opensoul --skill merge-pr-njx-njx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/NJX-njx/opensoul/tree/main/.agents/skills/merge-pr
Command: npx skills add https://github.com/NJX-njx/opensoul --skill merge-pr-njx-njx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of merging GitHub pull requests via squash, ensuring a safe and efficient workflow for maintaining main branch integrity.

Core Features & Use Cases

  • Automated PR Merging: Executes squash merges on pull requests after validation and preparation.
  • Cleanup Management: Removes associated worktrees and local branches post-merge to keep repository tidy.
  • Use Case: When reviewing a feature branch ready for integration, use this Skill to perform a safe squash merge and clean up residual artifacts without manual intervention.

Quick Start

Use the merge-pr skill to merge a specified PR after verifying all checks and preparing the branch.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I automate GitHub PR squash merges and branch cleanup?

You can automate GitHub PR squash merges by using a skill that executes the merge after validation and automatically removes associated worktrees and local branches to keep the repository tidy.

Do I need GitHub CLI configured to automate squash merging pull requests?

Yes, automating squash merging pull requests requires Git and GitHub CLI (gh) configured with appropriate permissions to ensure safe integration of feature branches into the main branch.

What is the best way to maintain main branch integrity when merging feature branches?

The best way to maintain main branch integrity is using an automated squash merge workflow with safety checks, ensuring fast, consistent, and safe integration of feature branches into main.

How does automated worktree and local branch removal work after a PR merge?

Automated cleanup management removes associated worktrees and local branches post-merge without manual intervention, ensuring residual artifacts are cleaned up immediately after the squash merge succeeds.

Can I use this squash merge automation for shared repositories with multiple developers?

Yes, this squash merge automation is designed specifically for developers managing shared repositories, providing consistent and safe integration of feature branches while maintaining main branch integrity.