github-pr-workflow

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

1|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/agtktID/indagis-agent --skill github-pr-workflow-agtktid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/agtktID/indagis-agent/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/agtktID/indagis-agent --skill github-pr-workflow-agtktid

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 on machines where the GitHub CLI is not installed. ## Core Features & Use Cases - Full PR Lifecycle Automation: Create branches with conventional naming, write Conventional Commits messages, push, and open PRs using either gh CLI or git plus curl against the GitHub REST API. - CI Monitoring and Auto-Fix: Poll commit statuses and check runs, download failed workflow logs, diagnose failures using a troubleshooting reference, patch code, and re-push until checks pass. - Merge Management: Squash, rebase, or merge-commit PRs via API, enable auto-merge through GraphQL, and clean up local and remote branches. - Use Case: After fixing a login redirect bug, an agent creates a fix/login-redirect-bug branch, commits with a conventional message, opens a PR, watches CI, auto-fixes a lint failure, and squash-merges once checks turn 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 if the GitHub CLI is installed. Otherwise, push your branch with git and send a POST request to the GitHub REST API pulls endpoint with your head branch, base branch, title, and body.

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

Run `gh pr checks --watch` to poll until checks finish. Without gh, query the commit status endpoint and check-runs endpoint for your HEAD SHA using curl with a GITHUB_TOKEN, polling every 30 seconds until the state is success or failure.

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

Yes, every gh operation has a curl equivalent 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, 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`. With curl, fetch the PR node_id from the REST API, then call the GraphQL enablePullRequestAutoMerge mutation. The repository must have auto-merge enabled in its settings.