skills.rest
nexus-a1
nexus-a1COMMUNITY
Explore all skills by this author →
GitHub

merge-release

Merge approved release PRs into target branches using pr-merge.sh.

Updated Mar 29, 2026
Search Tags:#workflow#github#release#merge#branch#pr#checks
One-click install
npx skills add https://github.com/nexus-a1/claude-skills --skill merge-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-release
Source: https://github.com/nexus-a1/claude-skills/tree/main/skills/merge-release
Command: npx skills add https://github.com/nexus-a1/claude-skills --skill merge-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates the final merge of an approved release PR into its target branch, enforcing pre-merge validation and conflict checks to ensure a clean release.

Core Features & Use Cases

  • End-to-end release PR merge with pre-flight checks, policy gates, and optional branch deletion.
  • Interactive or automated merge flows that respect approvals, checks, and mergeability.
  • Works with the shared release tooling (pr-merge.sh) to surface structured results and guide decision-making.

Quick Start

Run the /merge-release command after a release PR has been approved and is ready to merge.

Frequently Asked Questions about merge-release

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

FAQPage Schema
How do I automate merging an approved release PR into its target branch?▼

You can automate merging approved release PRs by running the /merge-release command, which invokes the shared pr-merge.sh tool to handle validation gates, conflict checks, and the final merge into target branches.

What happens if there are merge conflicts when merging a release branch?▼

If merge conflicts arise during a release branch merge, the Skill's pr-merge tooling surfaces structured results to guide conflict resolution and prevent an unsafe merge into the target branch.

Does this release merge workflow enforce GitHub PR checks and approvals?▼

Yes, the release merge workflow enforces GitHub PR checks and approvals by respecting policy gates and validation states through interactive or automated merge flows before completing the merge.

Can I automatically delete a release branch after merging the PR?▼

Yes, you can automatically delete a release branch after merging the PR by passing optional deletion flags to the pr-merge.sh tool during the merge-release command execution.

What is the best way to handle interactive vs automatic merge flows for release branches?▼

The best way to handle interactive or automatic merge flows for release branches is using the Skill's pr-merge tooling with --plan and --apply flags, which respects approvals and checks while supporting both merge decision modes.

When should I not use an automated merge step for a release PR?▼

You should not use an automated merge step for a release PR if pre-flight validation gates fail or unresolved conflicts exist, as the Skill requires explicit approvals and clean checks before merging.

Related Skills

Explore More Software Engineering Skills→
sanruizsanruiz

GitHub Release Workflow

Automate GitHub release workflows with pre-release checks, branch creation, version updates, and tagging.

Community
Advanced
TrainLCDTrainLCD
71

finalize-release

Orchestrate GitHub tag creation, release publishing, and master-to-dev branch synchronization.

Official
Advanced
pekralpekral

merge-github-pr

Merge eligible GitHub pull requests after validating mergeability, CI checks, and approvals.

Community
Intermediate
TheFJKTheFJK
2

merge-pipeline

Automate GitHub pull request merging with pre-flight checks and conflict resolution.

Community
Advanced