skills.rest
JKhyro
JKhyroCOMMUNITY
Explore all skills by this author →
GitHub

github-pr-workflow

Manage GitHub pull request lifecycle from branch creation to merge.

Updated Apr 2, 2026
Search Tags:#automation#git#github#merge#ci-cd#pull-request#gh-cli
One-click install
npx skills add https://github.com/JKhyro/HERMES-AGENT --skill github-pr-workflow-jkhyro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/JKhyro/HERMES-AGENT/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/JKhyro/HERMES-AGENT --skill github-pr-workflow-jkhyro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the manual friction of managing GitHub pull requests by guiding branch creation, commits, PR creation, CI monitoring, failure diagnosis, and merge steps in one repeatable workflow.

Core Features & Use Cases

  • Branch and commit flow: Create clean feature, fix, docs, or ci branches and write conventional commits.
  • PR creation and review automation: Open draft or ready PRs, request reviewers, add comments, and track progress with gh or REST fallbacks.
  • CI recovery and merge control: Inspect failing checks, read logs, apply fixes, re-run verification, and squash-merge when everything is green.
  • Use case: A developer can use this Skill to ship a bug fix from a local branch through CI resolution and into a merged GitHub PR without switching tools.

Quick Start

Use the github-pr-workflow skill to create a branch, open a pull request, watch CI, and merge it once 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 branch creation to merge?▼

Automating the GitHub pull request lifecycle involves creating branches, writing commits, opening PRs, monitoring CI, and handling merges. This workflow uses gh CLI or REST API fallbacks to cover feature, fix, docs, ci, and refactor operations end to end.

What is the best way to monitor CI status and inspect failing checks for a pull request?▼

Monitoring CI status requires authenticated GitHub access to track check progress and inspect failing logs. When checks fail, you can read logs, apply fixes, re-run verification in an auto-fix loop, and merge once everything turns green.

Does this PR workflow support both gh CLI and direct GitHub REST API access?▼

Yes, this PR workflow supports repositories using gh CLI or direct Git and GitHub REST API access. It requires authenticated GitHub access to perform branch operations, commit changes, request reviewers, and handle squash or auto-merge configurations.

Can I open draft pull requests and request reviewers automatically?▼

Yes, you can open draft or ready PRs and request reviewers automatically. The workflow guides PR creation, adds comments, and tracks progress using gh or REST fallbacks without needing to switch tools.

How do I handle CI recovery and auto-fix loops before a squash merge?▼

Handling CI recovery involves inspecting failing checks, reading logs, applying fixes, and re-running verification. This auto-fix loop repeats until checks pass, enabling a squash or auto-merge to finalize the pull request.

Related Skills

Explore More Software Engineering Skills→
jasonkneenjasonkneen
471

openclicky-repo-operator

Automate GitHub repository management with Git commands and the GitHub API.

Community
Advanced
me2reshme2resh
489

release-sync

Create a main-to-dev PR with `-X ours` after a squash-merge release.

Community
Advanced
arcasilesgrouparcasilesgroup
54

ai-pr

Automate governed pull request workflows with pre-push gates and squash merge.

Official
Advanced
DaddyElonMusk69DaddyElonMusk69

github-pr-workflow

Automate GitHub pull request creation, commits, and merging via CLI or REST API.

Community
Advanced