skills.rest
nbramia
nbramiaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

merge-pr

Validate PR readiness, squash-merge, delete remote branch, and update linked GitHub issues.

20|4|Updated Jan 7, 2026
Search Tags:#automation#workflow#github#issue-tracking#pull-request#ci-checks#merge-pr
One-click install
npx skills add https://github.com/nbramia/LifeOS --skill merge-pr-nbramia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/nbramia/LifeOS/tree/main/.agents/skills/merge-pr
Command: npx skills add https://github.com/nbramia/LifeOS --skill merge-pr-nbramia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually merging PRs and keeping upstream issues in sync is error-prone and time-consuming; this Skill automates the safe merge process and updates related issues with delivery details.

Core Features & Use Cases

  • Validate PR readiness: open status, non-conflicting mergeability, and all CI checks passing before merging.
  • Automate merging: squash-merge the PR and delete the remote branch after successful validation.
  • Update linked issues: post a concise progress update to all referenced issues with PR metadata and delivery summary.

Quick Start

Provide the PR number to merge and update all linked issues with delivery details.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I automatically merge a pull request only after CI checks pass?▼

To automatically merge a pull request, the system validates its open status, non-conflicting mergeability, and passing CI checks. Once validated, it performs a squash merge and deletes the remote branch.

What is the best way to update linked GitHub issues after a pull request is merged?▼

Updating linked GitHub issues after a merge involves posting a concise progress update to all referenced issues. The update includes PR metadata and a delivery summary to keep issue tracking in sync.

How does automated PR merging handle issue tracking and delivery progress?▼

Automated PR merging handles issue tracking by validating the PR, performing a squash merge, and then posting delivery progress updates to linked GitHub issues. It uses PR metadata and statuses to provide accurate tracking.

Can I use a squash merge to automatically close remote branches and update issue tracking?▼

Yes, you can use a squash merge to automatically close remote branches and update issue tracking. The workflow deletes the remote branch after a successful merge and posts delivery details to linked issues.

What happens if a pull request has merge conflicts during automated PR merging?▼

If a pull request has merge conflicts, the automated PR merging process will fail its readiness validation. The system requires non-conflicting mergeability and passing CI checks before proceeding with the merge.

Do I need to provide a PR number to automate pull request merges and update linked issues?▼

Yes, you need to provide the PR number to automate pull request merges and update linked issues. Supplying the PR number allows the workflow to locate the PR, validate readiness, merge, and post delivery details.

Related Skills

Explore More Software Engineering Skills→
genlayerlabsgenlayerlabs
10

pr-merge

Merge GitHub pull requests after validating CI status and mergeability.

Official
Advanced
shenxingyshenxingy
8

merge-pr

Squash-merge GitHub pull requests and delete remote and local branches.

Community
Intermediate
DeDuvaDeDuva
1

pr-lifecycle

Automate GitHub PR lifecycle from issue pickup to merge.

Community
Advanced
duanegoodnerduanegoodner

land

Merges a GitHub pull request via squash and removes the feature branch.

Community
Intermediate