github-pr-workflow

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

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill github-pr-workflow-chensihakniroth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/Chensihakniroth/ANAKOT-AGENT/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill github-pr-workflow-chensihakniroth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing pull requests involves repetitive manual steps across branching, committing, PR creation, CI monitoring, failure diagnosis, and merging, often requiring different tooling depending on whether the GitHub CLI is installed. ## Core Features & Use Cases - Full PR Lifecycle Automation: Covers branch creation with naming conventions, Conventional Commits, PR creation, CI status polling, and squash merging with branch cleanup. - Dual Auth Fallback: Every operation provides both the gh CLI command and a git + curl REST/GraphQL API fallback for machines without gh installed. - CI Auto-Fix Loop: Diagnoses failed checks from logs, applies fixes with file tools, pushes, and re-verifies, with a troubleshooting reference covering test, lint, type, build, permission, timeout, and Docker failures. - Use Case: After implementing a bug fix, an agent can branch, commit with a conventional message, open a PR using a ready-made template, watch CI, auto-fix a failing lint check, and squash-merge once 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 to the GitHub REST API pulls endpoint with your branch as head and main as base.

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

Run `gh pr checks` for a one-shot status or `gh pr checks --watch` to poll until completion. With curl, query the commit status endpoint and the check-runs endpoint for the latest commit SHA on your branch.

Can I use the GitHub API without the gh CLI installed?▼

Yes, every gh operation has a curl fallback using the GitHub REST API with a GITHUB_TOKEN for authentication. Auto-merge is the exception, requiring a GraphQL mutation since the REST API does not support it.

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 with `gh run view --log-failed` or the API logs endpoint to identify the specific failure signature.

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

With gh, run `gh pr merge --auto --squash --delete-branch`. Via the API, fetch the pull request node_id and call the GraphQL enablePullRequestAutoMerge mutation, which requires the repository to have auto-merge enabled in settings.