github-pr-workflow

Manage GitHub pull request lifecycles from branch creation through merge and cleanup.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction from managing GitHub pull requests by guiding you through branch creation, commits, PR creation, CI monitoring, failure recovery, and merge completion in one consistent workflow.

Core Features & Use Cases

  • Branch and Commit Workflow: Create feature or fix branches, make conventional commits, and prepare changes cleanly for review.
  • Pull Request Automation: Open, draft, label, review, comment on, and close pull requests using either gh or git plus curl fallback commands.
  • CI Monitoring and Recovery: Check build status, inspect failed logs, diagnose common pipeline issues, and apply fixes before re-running checks.
  • Merge and Cleanup: Merge with squash, enable auto-merge when available, delete branches, and return to a clean main branch state.
  • Use Case: A developer finishes a bug fix, opens a PR, waits for CI, resolves a failing test, and merges the change without leaving the workflow.

Quick Start

Ask the Skill to take your current git branch through GitHub pull request creation, CI monitoring, and merge using the best available method.

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?

Automating GitHub pull request workflows involves guiding branch creation, conventional commits, PR creation, CI monitoring, failure recovery, and merge completion. This Skill orchestrates the entire lifecycle using gh CLI or git plus curl as fallbacks.

Can I monitor CI pipeline status and fix failing checks within a GitHub PR workflow?

You can monitor CI pipeline status within the GitHub PR workflow by checking build statuses, inspecting failed logs, and diagnosing common pipeline issues. This Skill supports applying fixes and re-running checks in an automated auto-fix loop.

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

You do not strictly need the gh CLI to manage GitHub pull requests. This Skill requires authenticated GitHub access via a GitHub token, and utilizes git and curl as fallback commands for environments where gh is unavailable.

What's the best way to handle branch cleanup after merging a GitHub pull request?

Handling branch cleanup after a GitHub pull request merge involves squash merging, enabling auto-merge when available, deleting the feature branch, and returning to a clean main branch state. This Skill automates these post-merge cleanup steps.

How does pull request automation work for GitHub repositories without the gh CLI?

Pull request automation without the gh CLI works by using git commands combined with curl to interact directly with the GitHub API. This allows you to open, draft, label, review, comment on, and close pull requests through fallback methods.

Why does my automated GitHub pull request workflow fail to enable auto-merge?

Automated GitHub pull request workflows may fail to enable auto-merge if the repository settings disallow it or if branch protection rules are unmet. This Skill attempts to enable auto-merge when available before proceeding to squash merge.