github-pr-workflow

Automate GitHub PR workflows with branch creation, CI monitoring, and merging.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/tangzheng202202/hermes-skills --skill github-pr-workflow-tangzheng202202
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/tangzheng202202/hermes-skills/tree/main/01-coding-dev/github/github-pr-workflow
Command: npx skills add https://github.com/tangzheng202202/hermes-skills --skill github-pr-workflow-tangzheng202202

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill simplifies the GitHub pull request workflow by coordinating branch creation, PR automation, and CI monitoring, reducing manual coordination and context-switching during collaboration.

Core Features & Use Cases

  • Create and switch to a new feature branch
  • Open PRs with appropriate titles and descriptions using gh CLI or REST curl
  • Monitor CI status and automatically retry or fix simple issues
  • Merge PRs with proper checks and base-branch policies
  • Works with both gh CLI and git+curl approaches for environments without gh

Quick Start

Create a feature branch, open a PR, and watch CI results until success.

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 workflow from branch creation to merge?

You can automate a GitHub pull request workflow by coordinating local git branch creation, PR opening via gh CLI or REST curl, CI status polling, and final merge operations into the base branch.

Can I automate pull request creation and CI monitoring without installing the gh CLI?

Yes, you can automate pull request creation and CI monitoring without the gh CLI by using git and REST curl commands, provided you have a valid GitHub token to authenticate API requests.

Do I need a GitHub token to automate PR merges and monitor CI pipelines?

Yes, you need a GitHub token or a gh CLI installation to authenticate API requests, parse the git remote for owner and repo details, and automate CI monitoring and PR merges.

What is the best way to handle CI failures when automating a pull request lifecycle?

The best way to handle CI failures during a pull request lifecycle is to monitor CI status and automatically retry builds or apply simple fixes before attempting to merge the PR.

How does parsing a git remote help automate pull request workflows across different branches?

Parsing a git remote extracts the owner and repository information required by the gh CLI or REST curl, enabling automated PR creation, CI polling, and branch merges across collaborative projects.