github-pr-workflow

Automate GitHub PR workflows including branch creation, commits, PRs, CI monitoring, and merging.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AVOI-CEO/avoi-agent --skill github-pr-workflow-avoi-ceo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/AVOI-CEO/avoi-agent/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/AVOI-CEO/avoi-agent --skill github-pr-workflow-avoi-ceo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the GitHub PR lifecycle by automating branch creation, commits, PRs, CI status monitoring, and merging, reducing manual overhead.

Core Features & Use Cases

  • Branch creation, commit management, and PR lifecycle automation using gh CLI or a GitHub REST API fallback.
  • CI status monitoring, auto-fix guidance for failing checks, and smooth merging strategies for teams.
  • Use Case: A team needs to open a PR, run checks, auto-fix trivial failures, and merge when all checks pass, all with minimal manual clicks.

Quick Start

Create a new feature branch, push your changes, and open a PR using gh pr create.

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?

You can automate GitHub pull request workflows by using a script-driven process to handle branch creation, commit management, PR opening, CI status polling, and final merging. This reduces manual overhead across the entire PR lifecycle.

What is the best way to monitor CI status and auto-fix failing checks before merging a PR?

Monitoring CI status involves polling check results via the gh CLI or GitHub REST API. When checks fail, the workflow provides auto-fix guidance for trivial errors and applies smooth merging strategies once all statuses pass.

Can I automate pull request lifecycles if the gh CLI is unavailable?

Yes, you can automate pull request lifecycles without the gh CLI. The workflow implements a fallback mechanism that uses standard git commands combined with GitHub REST API endpoints to execute branch setup, PR creation, and merge operations.

How does CI status monitoring work during the GitHub PR lifecycle?

CI status monitoring works by deterministically polling check endpoints through the gh CLI or GitHub REST API. The script continuously tracks CI status, offers auto-fix guidance for failing checks, and proceeds with merging only when validations succeed.

Do I need the GitHub REST API to perform multi-step merge cycles for code reviews?

You do not strictly need the GitHub REST API for multi-step merge cycles. The workflow primarily uses the gh CLI for branch setup and merging, but automatically falls back to the GitHub REST API when gh is unavailable.