skills.rest
stars-end
stars-endOFFICIAL
Explore all skills by this author →
GitHub

merge-pr

Verify CI, approvals, and Beads issue state before guiding GitHub PR merges.

Updated Aug 27, 2026
Search Tags:#git#workflow#ci/cd#pull request#deployment#github#merge
One-click install
npx skills add https://github.com/stars-end/affordabot --skill merge-pr-stars-end
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/stars-end/affordabot/tree/main/.claude/skills/merge-pr
Command: npx skills add https://github.com/stars-end/affordabot --skill merge-pr-stars-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merging Pull Requests involves critical checks (CI, conflicts, approvals) and a precise workflow to ensure atomic issue closure and a clean master branch.

Core Features & Use Cases

  • Automated Merge Readiness Checks: Verifies CI status, merge conflicts, and working tree cleanliness, blocking if critical issues exist.
  • Atomic Issue Closure Verification: Critically verifies that the Beads issue was already closed at PR creation time, ensuring JSONL merges atomically with code.
  • Guided Human Merge: Provides clear, step-by-step instructions and a direct link to the GitHub web UI for a reliable "Squash and merge" operation.
  • Use Case: When your PR is ready to merge, simply say "merge the PR," and this Skill will perform all necessary checks, confirm issue closure, and guide you through the final merge steps on GitHub.

Quick Start

When your Pull Request is ready to be merged, simply say: "merge the PR"

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 pull request merges with CI checks?▼

Automated PR merging verifies CI status, merge conflicts, approvals, and issue closure before guiding you through a squash merge on GitHub. It blocks if critical prerequisites fail, ensuring safe, atomic merges to your main branch.

What checks does a PR merge workflow perform before merging?▼

Pre-merge checks verify CI pipeline success, absence of merge conflicts, required approvals, clean working tree state, and that the associated issue was closed before PR creation, ensuring deployment readiness.

Can I merge a pull request without manually verifying CI and approvals?▼

Yes. Automated merge preparation validates CI passes, approvals exist, and no conflicts remain, then provides direct GitHub web UI instructions. You retain control—the Skill guides rather than auto-merges.

Why verify issue closure before merging a pull request?▼

Verifying that the issue closed before PR creation ensures JSONL and code merge atomically. This prevents deployment of code without matching issue state, maintaining data consistency across your workflow.

What happens if my PR has unresolved CI failures or conflicts?▼

The merge readiness check blocks and reports blocking issues—failed CI, unresolved conflicts, or missing approvals. You must resolve these upstream before the Skill permits merge guidance.

Does PR merge automation work with GitHub squash and merge?▼

Yes. The Skill provides explicit step-by-step instructions and a direct link to GitHub's web UI for squash merging, ensuring consistent commit history on your main branch.

Related Skills

Explore More Software Engineering Skills→
wiggitywhitneywiggitywhitney

prd-done

Automate branch creation, commits, pull requests, merging, and issue closure via GitHub CLI.

Community
Advanced
VIPER-MetricsVIPER-Metrics
1

close-pr

Close pull requests after testing and finalize issues, wiki docs, and worktrees.

Official
Advanced
mvillmowmvillmow
18

verify-pr-ready

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

Community
Basic
dawsonblockdawsonblock

github-pr-workflow

Automate GitHub pull request workflows from branch creation to merging.

Community
Advanced