github-pr-workflow

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

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/ewtodd/son-of-anton --skill github-pr-workflow-ewtodd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/ewtodd/son-of-anton/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/ewtodd/son-of-anton --skill github-pr-workflow-ewtodd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing pull requests involves repetitive manual steps: creating branches, writing conventional commits, opening PRs, watching CI, diagnosing failures, and merging. This Skill guides an agent through the entire PR lifecycle with ready-to-run commands, including fallbacks for machines without the GitHub CLI. ## Core Features & Use Cases - Full PR Lifecycle: Covers branch creation, conventional commits, pushing, PR creation, CI monitoring, auto-fixing CI failures, and merging (squash, rebase, auto-merge). - Dual Auth Paths: Every operation shows the gh CLI command first, then a git + curl fallback using the GitHub REST and GraphQL APIs for environments without gh. - CI Auto-Fix Loop: A structured diagnose-fix-push-verify loop with a troubleshooting reference covering test, lint, type, build, permission, timeout, and Docker failures. - Use Case: Ask the agent to fix a bug and ship it — it creates a fix/ branch, commits with a conventional message, opens a PR with a structured body template, watches CI, fixes any failures, and squash-merges when green. ## Quick Start Create a pull request for my current changes, monitor the CI checks, fix any failures, and merge it when everything passes.

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 after pushing your branch with `git push -u origin HEAD`. Without the gh CLI, send a POST request with curl to the GitHub API pulls endpoint using a GITHUB_TOKEN, specifying head branch and base branch.

How to automatically fix failing CI checks on a pull request?▼

Fetch the failed run logs with `gh run view --log-failed` or by downloading the logs zip via the API, diagnose the error pattern (test, lint, type, or build failure), patch the code, commit, and push. Re-check CI status and repeat up to three attempts.

Can I manage GitHub PRs without the gh CLI installed?▼

Yes, every operation has a git plus curl fallback using the GitHub REST API with a GITHUB_TOKEN. PR creation, status checks, merging, and comments all work via curl; auto-merge additionally requires the GraphQL API.

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

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

Why does my GitHub Actions CI keep failing on lint or type checks?▼

Lint failures show file and line numbers from tools like flake8, ruff, or black; fix them by running the formatter locally or editing the flagged lines. Type errors from mypy require correcting signatures or argument types at the reported locations.