merge-pr

Merge approved pull requests and synchronize local repositories to the base branch.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill merge-pr-kapilvirenahuja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/plays/merge-pr
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill merge-pr-kapilvirenahuja

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

merge-pr completes the merge lifecycle safely by merging an approved pull request, updating your local checkout to the latest base branch, and removing the feature branch from both local and remote—without leaving stale branches behind.

Core Features & Use Cases

  • Guardrailed merge workflow: Validates you’re on a non-default branch, your working tree is clean, a PR exists for the current branch, and the PR is mergeable before proceeding.
  • Deterministic orchestration via agents: Delegates platform and Git-domain actions to the repo-orchestrator agent through JSON contracts, avoiding direct merge/checkout platform calls in the play itself.
  • Post-merge verification & evidence: Runs scenario checks to confirm the branch is deleted and the merge is reflected on the platform, then writes a delivery report (and optionally an evidence file).

Quick Start

Use the merge-pr skill after your pull request is approved to merge it, update your base branch locally, and delete the feature branch on both your machine and the platform.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I safely merge a pull request and clean up local and remote branches?

Safely merging a pull request requires verifying the PR is mergeable and the working tree is clean, then merging the PR, switching to the base branch with an upstream pull, and deleting the feature branch locally and remotely.

What checks are needed before merging a git pull request in an enterprise workflow?

Before merging a pull request, you must verify you are on a non-default branch, the working tree is clean, a PR exists for the current branch, and the PR is mergeable without conflicts to ensure reproducible local state.

How do I verify a pull request merge completed successfully and branches were deleted?

To verify a pull request merge completed, run scenario checks to confirm the feature branch is deleted locally and remotely, and the merge is reflected on the platform, optionally generating an evidence file or delivery report.

Does agentic orchestration work for automating git merge and branch cleanup tasks?

Agentic orchestration works for automating git merge and branch cleanup by delegating platform and Git-domain actions through JSON contracts, avoiding direct merge or checkout calls and ensuring deterministic execution.

What happens if my working tree is not clean when I try to merge a pull request?

If your working tree is not clean, the pull request merge workflow will halt because a clean working tree is a required guardrail to ensure local state remains reproducible and conflicts are avoided during base-branch switching.

Can I use automated branch cleanup for enterprise CI/CD readiness workflows?

Automated branch cleanup supports enterprise CI/CD readiness by synchronizing local repositories to the latest base branch and deleting feature branches on the remote, ensuring a clean and reproducible state for subsequent deployments.