github-pr-workflow

Manage GitHub pull request lifecycle with CLI or REST API fallbacks.

Updated May 10, 2026
One-click install
npx skills add https://github.com/Mateus2411/Hermes-PersonalBot --skill github-pr-workflow-mateus2411
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/Mateus2411/Hermes-PersonalBot/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/Mateus2411/Hermes-PersonalBot --skill github-pr-workflow-mateus2411

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the friction of managing a GitHub pull request lifecycle—creating branches and commits, opening PRs, monitoring CI, fixing failures, and merging—especially when you want both a GitHub CLI workflow and a REST API fallback.

Core Features & Use Cases

  • Create PRs and follow a disciplined lifecycle: Branch creation, committing with Conventional Commits, pushing, and opening PRs using either gh or curl.
  • Monitor and diagnose CI status quickly: Check overall PR/commit status and inspect workflow runs and logs to pinpoint failures.
  • Repair failing CI and merge safely: Provide an auto-fix loop pattern (analyze logs → patch files → commit → push → re-check) and merge via squash or enable auto-merge.

Quick Start

Use this skill to guide you through creating a feature branch, pushing it, opening a PR, watching CI checks until green, then squash-merging the PR into main.

Frequently Asked Questions about github-pr-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage the full GitHub pull request lifecycle from branch creation to merging?

To manage the GitHub pull request lifecycle, you create a feature branch, commit using Conventional Commits, push, and open a PR using either the GitHub CLI or REST API, then monitor CI checks and squash-merge into main.

Can I monitor CI status and fetch workflow logs via the GitHub API without the CLI?

Yes, you can monitor CI status without the CLI by using authenticated GitHub REST or GraphQL API calls to poll commit checks, fetch workflow runs, and retrieve logs to pinpoint failures.

What is the best way to automate fixing failing CI checks on a GitHub pull request?

The best way to fix failing CI checks is an auto-fix loop: analyze workflow logs, patch files, commit, push, and re-check CI status until green, then enable auto-merge.

Does this GitHub PR workflow require a specific Git repository setup or authentication?

Yes, this workflow requires a Git repository with an origin remote and authenticated GitHub access via the `gh` CLI or a `GITHUB_TOKEN` to execute API calls.

How do I enable auto-merge for a pull request using GraphQL or REST API?

You can enable auto-merge for a pull request by executing GitHub REST or GraphQL API calls to configure the merge method, allowing the PR to merge automatically once CI checks pass.

Why use GraphQL or REST API fallbacks for pull request management instead of the GitHub CLI?

Using GitHub REST or GraphQL API fallbacks for pull request management ensures reliable operation in environments where the GitHub CLI is unavailable, maintaining full lifecycle control.