github-pr-workflow

Automate GitHub pull request workflows from branch creation to merging.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/dawsonblock/HERMY --skill github-pr-workflow-dawsonblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/dawsonblock/HERMY/tree/main/hermes-agent-2026.4.23/skills/github/github-pr-workflow
Command: npx skills add https://github.com/dawsonblock/HERMY --skill github-pr-workflow-dawsonblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the full GitHub pull request lifecycle, enabling teams to move code from branch creation to merge without manual coordination.

Core Features & Use Cases

  • Branch creation, PR creation, and merging using gh or a git+curl fallback to manage PRs across repositories.
  • CI status monitoring and automated guidance to fix failures and keep PRs green.
  • Real-world workflows for code review, approvals, and merge strategies (merge, squash, rebase) across multiple projects.

Quick Start

Create a feature branch, push it, and use the guide to open a PR and track CI until merge.

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 GitHub pull request workflows from branch creation to merge?

You can automate GitHub pull request workflows by managing the entire lifecycle from branch creation and PR opening to CI status monitoring and merging using GitHub CLI or a git and curl fallback.

Can I monitor CI status and get guidance to fix failing checks on a pull request?

Yes, the workflow monitors CI status and provides automated guidance to help fix failures, ensuring your pull requests stay green and can proceed to merge.

Does this GitHub PR automation work without the GitHub CLI installed?

Yes, if the GitHub CLI is unavailable, the workflow falls back to using standard git commands and curl to manage pull requests, CI checks, and merge operations across repositories.

What is the best way to manage code review approvals and merge strategies across multiple repositories?

The best way is to automate these processes end-to-end, applying configured merge strategies like merge, squash, or rebase while coordinating code review approvals across multiple GitHub projects.

Can I enable auto-merge for GitHub pull requests using GraphQL?

Yes, the workflow supports optional auto-merge functionality for pull requests by utilizing GraphQL operations to complete the merge automatically once requirements are met.

Why would I need to automate end-to-end pull request coordination for my team?

Automating the full pull request lifecycle eliminates manual coordination overhead, allowing development teams to move code from branch creation to merge efficiently without managing individual steps.