skills.rest
panayiotism
panayiotismCOMMUNITY
Explore all skills by this author →
GitHub

merge

Merge open pull requests in dependency order and clean up branches.

79|9|Updated Dec 9, 2025
Search Tags:#github#merge#release-management#ci#pull-requests#branch-cleanup
One-click install
npx skills add https://github.com/panayiotism/claude-harness --skill merge-panayiotism
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/panayiotism/claude-harness/tree/main/skills/merge
Command: npx skills add https://github.com/panayiotism/claude-harness --skill merge-panayiotism

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge all open pull requests, close linked issues, delete feature branches, and clean up local and remote refs. Use when completing features, merging PRs after review, or finalizing a release cycle.

Core Features & Use Cases

  • Merge PRs in dependency order, respecting base/base-branch relationships and ensuring clean merge histories.
  • Close linked issues automatically when PRs are merged, and delete source branches both locally and remotely.
  • Perform post-merge housekeeping, including updating internal state and pruning stale references to keep the repository tidy.
  • Support pre-merge validations such as CI status, merge conflicts checks, and required approvals in order to safely complete releases.

Quick Start

Run the merge workflow to automatically merge eligible PRs and clean up branches after a feature is reviewed.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I automate merging multiple GitHub pull requests with branch dependencies?▼

Automating multi-PR merges resolves branch dependencies by validating CI checks and approvals, then merging pull requests sequentially in dependency order to ensure clean merge histories.

What is the best way to clean up feature branches after merging a GitHub pull request?▼

Post-merge branch cleanup deletes source branches both locally and remotely, closes linked issues automatically, and prunes stale references to keep the repository tidy.

Can I validate CI status and required approvals before merging a release cycle?▼

Pre-merge validations check CI status, required approvals, and merge conflicts before merging eligible pull requests, ensuring you safely complete releases without breaking integration.

How do I close linked issues automatically when merging a pull request?▼

Closing linked issues happens automatically when PRs are merged, simultaneously deleting feature branches and updating internal tracking state to maintain accurate project records.

Does merging dependent feature branches require pre-merge conflict checks?▼

Merge conflict checks are required for multi-PR release flows with base-branch dependencies, validating that feature branches integrate cleanly before executing the sequential merge.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
ngx-signal-formsngx-signal-forms
3

monitor-ci

Monitor Nx Cloud CI pipelines and apply self-healing fixes.

Official
Advanced
jasonkneenjasonkneen
471

clicky-repo-operator

Manage Git repositories and GitHub workflows via Composio MCP or gh tools.

Community
Advanced
pkuppenspkuppens

maintenance-cleanup

Clean up merged branches, worktrees, GitHub Actions runs, and tmp directories.

Community
Intermediate