github-pr-workflow

Create, update, and merge GitHub pull requests via CLI or REST API.

Updated Sep 1, 2021
One-click install
npx skills add https://github.com/unclehowell/unclehowell --skill github-pr-workflow-unclehowell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/unclehowell/unclehowell/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/unclehowell/unclehowell --skill github-pr-workflow-unclehowell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual management of the full pull‑request lifecycle—branch creation, committing, opening PRs, watching CI, fixing failures, and merging—requires many repetitive commands and context switches.

Core Features & Use Cases

  • Branch management: Create and switch to feature branches following conventional naming.
  • Commit workflow: Stage changes and create conventional commit messages.
  • Pull request creation: Open PRs via the GitHub CLI or, when unavailable, through git plus the GitHub REST API.
  • CI monitoring: Check combined status and individual GitHub Actions runs, with optional polling.
  • Automatic failure handling: Retrieve logs, diagnose issues, apply fixes, and re‑push until checks succeed.
  • Merge options: Perform squash, merge, or rebase merges, and optionally enable auto‑merge.

These capabilities let developers automate the entire PR process in both local and CI‑only environments.

Quick Start

Ask the skill to create a new feature branch, commit your changes, open a pull request, monitor CI, and merge when all checks pass.

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 entire GitHub pull request lifecycle from branch creation to merge?

You can automate the GitHub pull request lifecycle by chaining branch creation, conventional commits, PR opening, CI monitoring, and final merging into a single command sequence. This removes repetitive manual git commands and context switches.

Can I create and merge GitHub pull requests without the GitHub CLI installed?

Yes, you can create and merge pull requests without the GitHub CLI by falling back to standard git commands combined with the GitHub REST API using a personal token. This allows full PR automation in CI-only environments.

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

To fix failing CI checks automatically, retrieve the GitHub Actions logs, diagnose the failure, apply code fixes, and re-push the branch. The skill polls the combined status and repeats until all checks pass.

What is the best way to monitor GitHub Actions CI status before merging a pull request?

The best way to monitor CI status before merging is to check the combined status and individual GitHub Actions runs with optional polling. This ensures all checks succeed before triggering a squash, merge, or rebase.

Does this GitHub PR automation support squash, rebase, and auto-merge options?

Yes, this GitHub PR automation supports squash, merge, and rebase merges, and optionally enables auto-merge. It handles the final merge step automatically once all CI checks pass.

Why does manual pull request management slow down development workflows?

Manual pull request management slows development because it requires repetitive commands for branch creation, committing, opening PRs, watching CI, fixing failures, and merging. Automating this sequence eliminates constant context switching.