github-pr-workflow

Automates the GitHub pull request lifecycle from branch creation through CI monitoring and merge.

Updated May 13, 2026
One-click install
npx skills add https://github.com/superfhp/lumi-agent-body --skill github-pr-workflow-superfhp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/superfhp/lumi-agent-body/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/superfhp/lumi-agent-body --skill github-pr-workflow-superfhp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing pull requests involves many repetitive steps—branching, committing, opening PRs, watching CI, diagnosing failures, and merging—and doing them manually or inconsistently slows down development and introduces errors. ## Core Features & Use Cases - Full PR Lifecycle Automation: Create branches with naming conventions, write conventional commits, push, and open PRs using either the gh CLI or raw git + curl API calls. - CI Monitoring and Auto-Fix: Poll check statuses, download failure logs, diagnose common failure patterns (tests, lint, types, builds, permissions), and follow a structured fix-commit-push loop. - Flexible Merging: Squash, rebase, or merge-commit via CLI or REST/GraphQL API, including auto-merge enablement and branch cleanup. - Use Case: You fixed a login redirect bug. The skill guides the agent to branch, commit with a conventional message, open a PR with a structured body, watch CI, auto-fix a failing lint check, and squash-merge when green. ## Quick Start Ask the agent to create a branch, commit your current changes, open a pull request, monitor CI, and merge it once 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 create a GitHub pull request from the command line?▼

Use `gh pr create` with a title and body if the GitHub CLI is installed, or send a POST request to the GitHub REST API pulls endpoint with your token, head branch, and base branch. The skill detects which method is available automatically.

How to monitor GitHub Actions CI status for a pull request?▼

Run `gh pr checks --watch` to poll until checks finish, or query the commit status and check-runs API endpoints with curl using the branch's HEAD SHA. A polling loop every 30 seconds works when gh is unavailable.

Can I use GitHub PR automation without the gh CLI installed?▼

Yes, every operation has a git plus curl fallback using the GitHub REST API with a GITHUB_TOKEN. The token can be read from the environment, a .env file, or git-credentials, and auto-merge uses the GraphQL API.

Why does my GitHub Actions CI check keep failing?▼

Common causes include test assertion mismatches, lint or formatting violations, type errors, missing dependencies, permission issues, and timeouts. Download the failed run logs, match the error signature against known patterns, fix the code, and push again.

How do I enable auto-merge on a GitHub pull request?▼

With gh, run `gh pr merge --auto --squash`. Without gh, fetch the PR's node_id from the REST API and call the GraphQL enablePullRequestAutoMerge mutation. The repository must have auto-merge enabled in its settings.