github-pr-workflow

Automate the GitHub Pull Request lifecycle from branch creation to merging.

Updated May 16, 2026

Search Tags:#ci/cd #workflow automation #github #branching #pull requests #merge #github api

Ready to run

npx skills add https://github.com/jaredcroxton/hermes-mirror --skill github-pr-workflow-jaredcroxton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/jaredcroxton/hermes-mirror/tree/main/agents/skills/github/github-pr-workflow
Command: npx skills add https://github.com/jaredcroxton/hermes-mirror --skill github-pr-workflow-jaredcroxton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing a GitHub Pull Request lifecycle across branching, pushing, CI verification, and merging without getting stuck on tooling differences or API details.

Core Features & Use Cases

Branch, Commit, and PR Creation: Create feature branches, make conventional commits, push to origin, and open a PR using either gh or GitHub REST API calls.
CI Status Monitoring: Check combined commit status and GitHub Actions check runs, then poll until checks succeed or fail.
Auto-fix CI Failures and Merge: Diagnose CI failures via run logs, apply fixes using file tooling, re-run verification, and merge PRs (squash or auto) when green.

Quick Start

Use this workflow to create a PR, watch CI until it finishes, and then merge it using squash when all checks pass.

Frequently Asked Questions about github-pr-workflow

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

FAQPage Schema

How do I automate a GitHub pull request lifecycle from branching to merge?▼

Automating a GitHub pull request lifecycle involves creating feature branches, committing, pushing, opening PRs, polling CI status checks, and merging via `gh` CLI or GitHub REST API fallback. This workflow manages the full process end-to-end.

Do I need the GitHub CLI installed to automate pull request creation and merging?▼

You do not strictly need the GitHub CLI installed to automate pull request creation. The workflow attempts to use `gh` first and falls back to standard git commands combined with GitHub REST API curl calls for consistent behavior.

What is the best way to monitor GitHub Actions CI status before merging a pull request?▼

The best way to monitor GitHub Actions CI status is to check the combined commit status and check runs, then poll until checks succeed or fail. This workflow handles polling automatically and merges PRs when checks pass.

How do I diagnose CI failures and auto-fix failing GitHub Actions workflow runs?▼

To diagnose CI failures and auto-fix failing GitHub Actions workflow runs, retrieve workflow run logs to identify errors, apply file fixes, re-run verification, and merge when green. This workflow automates that diagnostic process.

Can I extract the repository owner and name automatically from git remote for API calls?▼

Yes, you can extract the repository owner and name automatically from the git remote. The workflow requires authenticated GitHub access and parses remote details to construct API requests for PR creation and CI monitoring.