skills.rest
magicpro97
magicpro97COMMUNITY
Explore all skills by this author →
GitHub

merge-when-green

Automatically merge GitHub pull requests after all required CI checks pass.

8|3|Updated Jun 7, 2026
Search Tags:#code review#PR management#CI integration#GitHub automation#merge automation
One-click install
npx skills add https://github.com/magicpro97/vibeflow --skill merge-when-green
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-when-green
Source: https://github.com/magicpro97/vibeflow/tree/main/.vibeflow/skills/merge-when-green
Command: npx skills add https://github.com/magicpro97/vibeflow --skill merge-when-green

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manages the PR merge queue by ensuring all CI checks pass before automatically merging pull requests, reducing the risk of merging broken code.

Core Features & Use Cases

  • CI Check Enforcement: Enforces that all required CI checks must pass before merging.
  • Merge Gate: Ensures both check and publish jobs pass, along with no merge conflicts.
  • Human Verification: Optionally prompts for human verification before merging.
  • Use Case: A team uses this Skill to automate the merging of pull requests in their repository only when all automated checks have passed and human verification is complete.

Quick Start

Enable the merge-when-green skill and trigger a merge when the pull request is ready to be merged.

Frequently Asked Questions about merge-when-green

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

FAQPage Schema
How do I automate GitHub PR merging only when CI checks pass?▼

To automate PR merging only when CI checks pass, you can use a merge automation tool that monitors pull request statuses and merges them automatically once all required checks succeed, reducing the risk of merging broken code.

What is a merge gate and how does it work with CI pipelines?▼

A merge gate ensures both `check` and `publish` jobs pass, along with verifying no merge conflicts, before allowing a pull request to merge. It works by monitoring your CI pipeline status via the GitHub API to enforce CI check compliance.

Can I require human verification before a pull request is automatically merged?▼

Yes, you can optionally prompt for human verification before merging. This allows teams to automate CI check enforcement while maintaining manual oversight before code is integrated into the repository.

Do I need GitHub API access to automate pull request management?▼

Yes, GitHub API access is required to monitor pull request statuses and automate merging. A proper CI/CD pipeline setup is also necessary to enforce that required checks pass before the merge occurs.

Why does my automated PR merge fail when CI checks are green?▼

Automated PR merges can fail even when checks are green if there are merge conflicts. The merge gate requires both `check` and `publish` jobs to pass and verifies no merge conflicts exist before merging.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
coco-researchcoco-research
264

finishing-a-development-branch

Verify tests, then merge, pull request, keep, or discard a development branch.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate
jamescjamesc

review-code

Review current branch changes against main with multi-pass analysis.

Community
Advanced