github-pr-workflow

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

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/maopujie10-sys/Bailongma --skill github-pr-workflow-maopujie10-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/maopujie10-sys/Bailongma/tree/main/skills/hermes-skills/github/github-pr-workflow
Command: npx skills add https://github.com/maopujie10-sys/Bailongma --skill github-pr-workflow-maopujie10-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing pull requests involves many repetitive steps—creating branches, writing conventional commits, opening PRs, watching CI, fixing failures, and merging—and doing them manually or inconsistently slows down development and introduces errors. ## Core Features & Use Cases - Full PR Lifecycle Automation: Covers branch creation with naming conventions, Conventional Commits, PR creation, CI status monitoring, auto-fixing CI failures, and merging with squash or auto-merge. - Dual Tooling Support: Every operation is shown with both the gh CLI and a git + curl fallback using the GitHub REST/GraphQL APIs, so it works on machines without gh installed. - CI Auto-Fix Loop: Provides a structured diagnose-fix-push-verify loop for resolving failing checks, including downloading and reading failed workflow logs. - Use Case: You fixed a login redirect bug on a feature branch. Use this Skill to commit with a conventional message, push, open a PR that closes the related issue, poll CI until green, and squash-merge with branch cleanup. ## Quick Start Create a pull request for my current branch, monitor its CI checks, fix any failures, and squash-merge it 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 create a GitHub pull request from the command line?

Use `gh pr create` with a title, body, and optional flags like --draft, --reviewer, and --base. Without gh, push your branch and send a POST request to the GitHub REST API pulls endpoint with your token, head branch, and base branch.

How to check GitHub Actions CI status for a pull request?

Run `gh pr checks` for a one-shot view or `gh pr checks --watch` to poll until completion. With curl, query the commit status endpoint and the check-runs endpoint for the branch HEAD SHA to see each check's state and conclusion.

Can I use GitHub API without the gh CLI installed?

Yes, every gh operation has a git plus curl equivalent using the GitHub REST API with a token from GITHUB_TOKEN, a .env file, or git-credentials. Auto-merge additionally requires the GraphQL API since REST does not support it.

How do I automatically fix failing CI checks on a PR?

Follow the auto-fix loop: list workflow runs, download failed job logs, identify the error, patch the code with file tools, commit and push, then re-check CI status. Repeat up to three attempts before asking the user.

What merge methods does the GitHub API support for pull requests?

The merge endpoint supports merge commit, squash, and rebase methods via the merge_method field. Squash merging with branch deletion is recommended for feature branches, and auto-merge can be enabled through the GraphQL API when repository settings allow it.