skills.rest
genlayerlabs
genlayerlabsOFFICIAL
Explore all skills by this author →
Website𝕏@genlayerGitHub

pr-merge

Merge GitHub pull requests after validating CI status and mergeability.

10|6|Updated Jan 29, 2026
Search Tags:#automation#workflow#github#merge#pr#ci
One-click install
npx skills add https://github.com/genlayerlabs/skills --skill pr-merge-genlayerlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-merge
Source: https://github.com/genlayerlabs/skills/tree/main/.claude/skills/pr-merge
Command: npx skills add https://github.com/genlayerlabs/skills --skill pr-merge-genlayerlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of merging GitHub pull requests, ensuring that all Continuous Integration (CI) checks pass and that the merge state is clean, preventing broken code from being merged.

Core Features & Use Cases

  • Strict CI Validation: Never merges a pull request if CI checks have failed.
  • Merge State Checking: Verifies the PR is not behind the main branch, has no conflicts, and meets review requirements before merging.
  • Automated Branch Updates: Updates the branch if it's behind the main branch.
  • Use Case: When a developer finishes their work and wants to merge their feature branch into main, they can use this skill to ensure the merge is safe and compliant with project standards.

Quick Start

Use the pr-merge skill to merge the pull request for the current branch.

Frequently Asked Questions about pr-merge

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

FAQPage Schema
How do I safely merge a GitHub pull request without bypassing CI checks?▼

To safely merge a GitHub pull request, you must validate CI status and mergeability programmatically. This skill checks PR state, CI status, and merge conflicts, strictly enforcing a policy against bypassing failed CI checks before merging.

What happens if my pull request is behind the main branch when I try to merge?▼

When a pull request is behind the main branch, the merge state is not clean. This skill handles this scenario by automatically updating the branch to ensure it is current before proceeding with the merge validation.

Can I merge a GitHub PR if my CI checks have failed?▼

No, you cannot merge a GitHub PR if CI checks have failed. This skill enforces strict CI validation and never allows merging broken code, only permitting review bypass when all other CI checks pass.

How do I automate merging feature branches into main with GitHub CLI?▼

You automate merging feature branches into main by programmatically interacting with the GitHub CLI. This skill validates the PR state, verifies CI status, and ensures the merge state is clean to prevent broken code from merging.

Does the PR merge process verify review requirements and conflicts before merging?▼

Yes, the PR merge process verifies review requirements and conflicts before merging. It checks the PR merge state to ensure there are no conflicts and that review requirements are met before proceeding.

When should I not use an automated workflow to merge a pull request?▼

You should not use an automated workflow to merge a pull request if you need to bypass failed CI checks. This skill enforces a strict policy against merging when CI fails, only allowing review bypass when all other checks pass.

Related Skills

Explore More Software Engineering Skills→
proven-xyzproven-xyz
2

pr-merge

Merge GitHub pull requests with squash after CI checks pass.

Official
Advanced
nikhilsitaramnikhilsitaram
89

pr-merge

Merge reviewed GitHub pull requests and clean up branches and worktrees.

Community
Advanced
KanakMalpaniKanakMalpani

springboot-verification

Run build, static analysis, tests, security scans, and diff review for Spring Boot projects.

Community
Advanced
mvillmowmvillmow
18

verify-pr-ready

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

Community
Basic