github-pr-workflow

Automate the GitHub pull request lifecycle from branch creation to merging.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/1thirteeng3/greenmoire --skill github-pr-workflow-1thirteeng3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/1thirteeng3/greenmoire/tree/main/integrations/hermes-agent/skills/github/github-pr-workflow
Command: npx skills add https://github.com/1thirteeng3/greenmoire --skill github-pr-workflow-1thirteeng3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Complete automation of the GitHub pull request lifecycle to reduce manual toil, minimize human error, and accelerate delivery by orchestrating branch creation, PR generation, CI monitoring, auto-fixes, and merges.

Core Features & Use Cases

  • Branch management: create feature branches, sync with the main branch, and enforce conventional naming.
  • PR automation: open PRs, update descriptions, request reviews, and merge when checks pass.
  • CI visibility & auto-fix: monitor status checks, retrigger failed steps, and apply remediation actions per policy described in the SKILL.md.

Quick Start

Create a feature branch, push it, open a PR, and let the workflow manage checks and merge when 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 the GitHub pull request lifecycle from branch creation to merge?

The GitHub PR workflow automates pull request lifecycles by orchestrating branch creation, PR generation, CI monitoring, and merges via gh CLI or REST API. It reduces manual toil by enforcing deterministic pipelines across forks and branches.

Can I use gh CLI to monitor CI status checks and apply auto-fixes?

Yes, you can use gh CLI or curl-based REST API flows to monitor CI status checks. The workflow retriggers failed steps and applies remediation actions based on policies defined in the provided SKILL.md instructions.

Does this GitHub PR workflow support multiple environments and repository forks?

Yes, the workflow supports deterministic PR pipelines across forks, branches, and multiple CI environments. It orchestrates git operations and GitHub API interactions to satisfy requirements for teams needing cross-fork automation.

What is the best way to enforce conventional branch naming and sync feature branches with main?

The best way to enforce conventional branch naming and sync feature branches with main is through automated branch management. This workflow handles feature branch creation, syncing with the main branch, and naming conventions end-to-end.

Why should I use an automated PR workflow instead of manually merging pull requests?

Automating the PR workflow reduces manual toil, minimizes human error, and accelerates delivery. It provides deterministic pipelines for opening PRs, updating descriptions, requesting reviews, and merging only when CI checks pass.