github-pr-workflow

Manage GitHub pull request lifecycle with branch creation, CI monitoring, and merging.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Rheasilvia/hermes-desktop --skill github-pr-workflow-rheasilvia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/Rheasilvia/hermes-desktop/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/Rheasilvia/hermes-desktop --skill github-pr-workflow-rheasilvia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, curl, python3, and includes references (resource) components.

What problem does it solve?

This skill removes the friction from managing GitHub pull requests by providing a unified, automated workflow that handles branching, committing, CI monitoring, and merging, regardless of whether you use the GitHub CLI or standard Git and cURL commands.

Core Features & Use Cases

  • Unified PR Lifecycle: Standardizes the process of creating, monitoring, and merging pull requests using either the gh CLI or native API calls.
  • Automated CI/CD Handling: Provides robust logic to monitor CI status, diagnose failures, and perform auto-fixes for common issues like linting or test errors.
  • Use Case: When a developer pushes a new feature, this skill can automatically open a PR, wait for the CI pipeline to pass, and perform a squash merge once the checks are green, ensuring a clean and consistent repository history.

Quick Start

Use the github-pr-workflow skill to create a new pull request for the current branch and monitor the CI status until the merge is complete.

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 merging after CI passes?

Automate GitHub pull request merging by monitoring CI status via the GitHub REST or GraphQL APIs, diagnosing failures, and performing a squash merge once checks pass to ensure a clean repository history.

Can I manage GitHub pull requests without the gh CLI installed?

Yes, you can manage GitHub pull requests without the gh CLI by using standard git and curl commands to interface directly with the GitHub REST and GraphQL APIs for branch creation and merging.

What is the best way to standardize pull request commits across a development team?

Standardize pull request commits by enforcing a unified PR lifecycle workflow that handles branch creation, commit standardization, and automated merging regardless of the local repository setup.

Does this GitHub PR workflow handle CI pipeline failures automatically?

Yes, the GitHub PR workflow handles CI pipeline failures by monitoring CI status, diagnosing failures, and performing auto-fixes for common issues such as linting or test errors.

Do I need Python to monitor CI status and manage pull requests?

Yes, you need Python3 installed along with git and curl to run the logic that monitors CI status and manages the end-to-end lifecycle of your GitHub pull requests.

Why does my automated pull request workflow fail to merge branches?

Automated pull request workflows fail to merge branches when CI checks do not pass, requiring the system to diagnose failures and attempt auto-fixes for linting or test errors before merging.