github-pr-workflow

Manage GitHub pull requests from branch creation to merge.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of managing pull requests by guiding you through branch creation, commit hygiene, PR submission, CI monitoring, failure recovery, and final merge decisions in one workflow.

Core Features & Use Cases

  • Branch and Commit Workflow: Create a clean feature branch, make conventional commits, and prepare changes for review with consistent PR messaging.
  • PR Lifecycle Management: Open pull requests, track check status, inspect failed runs, and apply fixes when CI or validation steps fail.
  • Merge and Cleanup: Complete the workflow by merging with the preferred strategy, enabling auto-merge when appropriate, and cleaning up local and remote branches.
  • Use Case: A developer finishes a bug fix, asks the Skill to open the pull request, watches CI until it passes, and then merges the change without switching tools.

Quick Start

Ask the skill to create a branch from main, open a pull request for your change, monitor CI, and merge it once checks are green.

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?

To automate a GitHub pull request workflow, you create a feature branch, make conventional commits, open the PR, monitor CI check status, diagnose failures, and apply the final merge. This manages the full lifecycle from branch creation to merge in one continuous process.

What should I do when CI checks fail on my pull request?

When CI checks fail on your pull request, you should inspect the failed runs to diagnose the failure. The workflow supports applying fixes directly within the same environment, allowing you to update the PR and re-trigger validation without switching tools.

Do I need the GitHub CLI installed to manage pull requests end to end?

You do not strictly need the GitHub CLI, as the workflow supports a curl-based fallback for REST API operations. However, having authenticated GitHub access, a git repository context, and either gh or curl available is required to create, inspect, update, and merge pull requests.

Can I enable auto-merge for a GitHub pull request after CI passes?

Yes, you can enable auto-merge for a GitHub pull request when appropriate. The workflow supports completing the process by merging with your preferred strategy, enabling auto-merge, and cleaning up both local and remote branches afterward.

What is the best way to handle branch cleanup after merging a pull request?

The best way to handle branch cleanup after merging a pull request is to delete both the local and remote feature branches as part of the final merge and cleanup stage. This ensures the repository remains clean after the change is merged.