github-pr-workflow

Automates branching, committing, pull request creation, CI monitoring, and merging on GitHub.

33|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/infinition/LaRuche --skill github-pr-workflow-infinition
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/infinition/LaRuche/tree/main/laruche/skills/github-pr-workflow
Command: npx skills add https://github.com/infinition/LaRuche --skill github-pr-workflow-infinition

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing the full pull request lifecycle manually is error-prone: malformed PR bodies, polling the wrong CI endpoint, and unsafe merge or branch-deletion habits cause wasted time and broken workflows. This Skill guides an agent through the entire branch-to-merge process with correct commands for both gh and plain git plus curl. ## Core Features & Use Cases - End-to-End PR Lifecycle: Covers branching with intent prefixes, Conventional Commits, PR creation, CI polling via the check-runs API, failure diagnosis, merging, and cleanup. - Dual Tooling Paths: Every step is provided with both the gh CLI and REST/GraphQL curl equivalents for servers without gh installed. - CI Troubleshooting Reference: Includes a catalog of common CI failure signatures (tests, lint, types, builds, permissions, timeouts, Docker) with diagnosis and fixes. - Use Case: You ask the agent to ship a bug fix. It creates a fix/ branch, commits with a conventional message, opens a PR using the bugfix template, watches CI, diagnoses a failing lint job from the logs, pushes a fix, and squash-merges once checks pass. ## Quick Start Create a pull request for my current changes, watch 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?▼

Push your branch first with git push -u origin HEAD, then run gh pr create with a title and body. Without gh, send a POST request to /repos/OWNER/REPO/pulls with the head branch, base branch, title, and body serialized as JSON.

How do I check GitHub Actions CI status via the API?▼

Query the /commits/SHA/check-runs endpoint, not the legacy /status endpoint. The status endpoint only reports external commit statuses and returns pending forever on repositories using GitHub Actions, while check-runs reports actual job conclusions.

Why does my GitHub PR creation return 422 Validation Failed?▼

A 422 usually means a PR already exists for the head branch, head and base are identical, or the body was malformed JSON. Read the errors array in the API response, which names the exact field that failed validation.

Can I enable auto-merge on a pull request with curl?▼

Auto-merge has no REST endpoint; it requires the GraphQL API. Fetch the pull request's node_id, then call the enablePullRequestAutoMerge mutation with your desired merge method such as SQUASH.

Why won't my branch delete after merging a pull request?▼

Squash merges rewrite commits, so git cannot see the branch's commits in main and git branch -d refuses. Confirm the PR is merged on GitHub first, then use git branch -D, which is the one case where force-deletion is correct.

What should I do when CI keeps failing after multiple fix attempts?▼

Stop after three failed fix attempts, since repeated failure means the diagnosis is wrong. Reproduce the failure locally before pushing, and if it only fails in CI, treat the environment difference itself as the bug.