github-merge-pr

Monitor GitHub pull request CI status and merge after checks pass.

Updated Oct 15, 2021
One-click install
npx skills add https://github.com/toqoz/config --skill github-merge-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-merge-pr
Source: https://github.com/toqoz/config/tree/main/home/agents/skills/github-merge-pr
Command: npx skills add https://github.com/toqoz/config --skill github-merge-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This skill eliminates the manual overhead of monitoring CI pipelines, resolving minor test failures, and performing final code reviews before merging pull requests.

Core Features & Use Cases

  • Automated CI Monitoring: Watches PR status and identifies failures in real-time.
  • Self-Healing: Automatically attempts to fix common CI issues like linting or formatting errors.
  • Safety Guardrails: Integrates with Codex for final diff reviews and ensures all required checks pass before merging.
  • Use Case: A developer pushes a branch and triggers this skill to handle the entire lifecycle of the PR, from waiting for tests to passing to final merge, without further manual intervention.

Quick Start

Invoke the github-merge-pr skill to monitor the current branch and automatically merge the pull request once all checks pass and the review is complete.

Frequently Asked Questions about github-merge-pr

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

FAQPage Schema
How do I automate GitHub pull request merging after CI passes?

You can automate GitHub pull request merging by invoking this skill to monitor the current branch, wait for CI checks to pass, and automatically merge the PR without manual intervention.

Can I automatically fix CI failures like linting errors in a pull request?

Yes, this skill provides self-healing capabilities that automatically attempt to resolve common CI issues such as linting or formatting errors directly within your pull request workflow.

Do I need the GitHub CLI to automate PR verification and merging?

Yes, you need the GitHub CLI (gh) installed because this skill requires it to interact with the GitHub API for monitoring CI status and performing conditional merges.

What is the best way to ensure required checks pass before merging a PR?

The best way to ensure safety is using this skill's guardrails, which integrate with Codex for final diff reviews and verify that all required CI checks pass before merging the pull request.

Does automated PR merging work with Codex CLI for code review?

Yes, automated PR merging works with optional Codex CLI integration to perform final code reviews on diffs, ensuring an additional layer of safety before the conditional merge is executed.