github-pr-workflow

Automate GitHub pull request lifecycle and CI monitoring via CLI or REST API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing pull requests across branch creation, commits, CI monitoring, failure diagnosis, and merging is repetitive and error-prone for developers and automation agents. This Skill provides a step-by-step, reproducible workflow to create branches, push changes, open PRs, monitor CI, attempt automated fixes, and perform merges with safe fallbacks.

Core Features & Use Cases

  • Branching & Commits: Standardized branch naming, checkout, and commit guidance to keep histories clean.
  • PR Creation: Create pull requests using the gh CLI or a git plus curl REST API fallback when gh is unavailable.
  • CI Monitoring & Auto-Fix Loop: Poll CI status, fetch workflow logs, diagnose failures, apply fixes, and re-run checks following a bounded retry pattern.
  • Merging Strategies: Support for squash, merge commit, rebase, and enabling auto-merge when repository settings allow.
  • Use Case: A developer fixes a failing test, pushes a branch, opens a PR, uses the auto-fix loop to resolve CI failures, and merges once checks are green.

Quick Start

Create a branch, make and commit your changes, push and open a pull request, monitor CI until green, and merge with your chosen 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 lifecycle management from the command line?

You can automate the GitHub pull request lifecycle by creating branches, committing changes, opening PRs, and merging via the gh CLI or a git plus REST API fallback to streamline repetitive developer workflows.

How do I automatically fix failing CI checks in a GitHub pull request?

To fix failing CI checks in a GitHub pull request, you can use an automated loop that polls CI status, fetches workflow logs, diagnoses failures, applies code fixes, and re-runs checks within a bounded retry pattern.

What is the best way to monitor GitHub Actions CI status and merge a PR automatically?

The best way to monitor GitHub Actions CI status and merge a PR is to poll check statuses until green, then execute a merge using squash, merge commit, or rebase strategies, or enable auto-merge if repository settings allow.

Do I need the gh CLI installed to create and merge GitHub pull requests via API?

You do not need the gh CLI installed to create and merge GitHub pull requests, as the workflow supports a git plus GitHub REST API fallback using curl, provided you have a valid Git remote and authentication token.

What are the limitations of automating GitHub PR merges with REST API fallbacks?

Limitations of automating GitHub PR merges with REST API fallbacks include requiring a valid Git remote and authentication token for API calls, and relying on repository settings to permit specific merge strategies or auto-merge enablement.