git-workflow-pr-ready

Guides bringing open pull requests to readiness by lifting drafts and fixing red CI runs.

1|Updated Jan 14, 2024
One-click install
npx skills add https://github.com/Eyhenij/rt-tools --skill git-workflow-pr-ready-eyhenij
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow-pr-ready
Source: https://github.com/Eyhenij/rt-tools/tree/main/.claude/skills/git-workflow-pr-ready
Command: npx skills add https://github.com/Eyhenij/rt-tools --skill git-workflow-pr-ready-eyhenij

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open pull requests often linger as drafts or with failing CI runs while developers move on to new tasks, leaving work invisible or unfinished for reviewers. This Skill defines the discipline for finishing handed-over work first: reading run states, lifting drafts, and fixing failures in the correct branch of a PR chain. ## Core Features & Use Cases - Draft lifecycle management: Lift draft status with gh pr ready in the same turn a green run is read, so completed work is actually handed over. - Red run diagnosis: Analyze failed CI runs step-by-step using gh pr checks and gh api to identify the exact failing step as the diagnosis. - Chain-aware fixing: Fix shared causes in the lowest branch of a PR chain and propagate upward by merging (never rebasing), one branch at a time. - Use Case: You have three chained PRs open, one red and two still drafts. This Skill directs you to read all run states, lift the green drafts, fix the failure in the lowest branch, and merge the fix upward through the chain before taking any new task. ## Quick Start Ask the assistant to check the state of all open pull requests, lift any drafts with green runs, and diagnose and fix the failing run starting from the lowest branch in the chain.

Frequently Asked Questions about git-workflow-pr-ready

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I mark a draft pull request as ready on GitHub?

Run `gh pr ready <number>` from the GitHub CLI to lift the draft state. This should happen in the same turn the green CI run is read, since lifting the draft is the final step of handing the work over.

How do I diagnose a failing CI run on a pull request?

Run `gh pr checks <number>` to find the failed run, then query `gh api` on that run filtering steps with `select(.conclusion=="failure")`. The failed step name is the diagnosis for where to fix.

Should I fix a failing check in the branch where it went red?

No. In a stacked PR chain, fix the cause in the lowest branch where it originated, then propagate upward by merging. Fixing from an upper branch leaves everything below it still red.

Why should I merge instead of rebase when updating stacked PR branches?

Rebasing rewrites the history of branches already handed over, causing the host to close upper PRs as merged even though main contains none of their edits. Merging preserves the handed-over history.

What does an empty CI run on a pull request mean?

An empty run means the event never reached the pipeline, often because a chain PR's base is not the main branch and the base filter blocked it. Treat it like a red run, not a green one.