draft-prs

Manage draft status of stacked GitHub Pull Requests.

Updated Feb 22, 2026

Search Tags:#git #ci/cd #code review #pull request #workflow automation #github

Ready to run

npx skills add https://github.com/jpeggdev/buildwithjpegg --skill draft-prs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: draft-prs
Source: https://github.com/jpeggdev/buildwithjpegg/tree/main/plugins/development-workflow/skills/draft-prs
Command: npx skills add https://github.com/jpeggdev/buildwithjpegg --skill draft-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that only the most relevant Pull Request (PR) in a stack is visible for review, preventing reviewers from wasting time on dependent work that isn't ready.

Core Features & Use Cases

Automated Draft Status: Automatically sets downstream PRs to 'draft' and promotes the next PR to 'open' when a base PR merges.
Dependency Management: Clearly communicates PR dependencies within the PR body.
Use Case: In a feature branch that requires multiple sequential PRs, this skill ensures that only the first PR is open for review, while subsequent PRs are marked as drafts until the preceding one is merged.

Quick Start

Use the draft-prs skill to manage the draft status of stacked pull requests.

Frequently Asked Questions about draft-prs

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

FAQPage Schema

How do I manage stacked pull request status on GitHub?▼

Manage stacked pull request status by automatically setting downstream PRs to draft and promoting the next PR to open when the base merges. This ensures only the bottom-most unmerged PR in a stack is visible for review.

Why should downstream PRs be marked as draft in sequential feature development?▼

Downstream PRs are marked as draft to prevent reviewers from wasting time on dependent work that isn't ready. This enforces a rule where only the bottom-most unmerged PR in a stack is open for review until preceding PRs merge.

How do I automate draft status for stacked GitHub Pull Requests?▼

Automate draft status for stacked GitHub Pull Requests by applying a skill that sets sequential PRs to draft and promotes them to open automatically when their base PR merges, streamlining the workflow.

Does this stacked PR workflow work with CI/CD and code review processes?▼

Yes, this stacked PR workflow integrates with CI/CD and code review processes by ensuring only the base-ready PR is open for review, clearly communicating PR dependencies within the PR body to guide reviewers.

What is the best way to handle PR dependencies in a stacked branch workflow?▼

Handle PR dependencies in a stacked branch workflow by enforcing a rule where only the first PR is open while subsequent PRs are drafts, clearly communicating these dependencies within the PR body until preceding PRs merge.

When should I not use automated draft status for stacked PRs?▼

Avoid using automated draft status for stacked PRs when your workflow does not involve sequential feature development or PR merging, as the rule enforcing only the bottom-most unmerged PR to be open requires a strict dependency stack.