pr-creation-flow

Orchestrate pull request lifecycle stages through a shell-based state machine.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill pr-creation-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-creation-flow
Source: https://github.com/kriscendobot/garden/tree/main/skills/pr-creation-flow
Command: npx skills add https://github.com/kriscendobot/garden --skill pr-creation-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the problem of fragmented and stalled pull request workflows by providing a deterministic, state-machine-driven process that ensures every PR is properly built, tested, reviewed, and un-drafted without manual intervention.

Core Features & Use Cases

  • Automated PR Lifecycle: Manages the entire chain from initial draft creation to final un-drafting for maintainer review.
  • Idempotent Job Handling: Uses markers and branch-tracking to prevent duplicate PRs and handle re-claimed jobs safely.
  • Integrated Review Panels: Automatically routes changes to the appropriate code or design panels based on the PR's file surface.
  • Use Case: A gardener can claim a build job to automatically open a draft PR, run tests, trigger the panel review, and move the PR to the maintainer's queue once all criteria are met.

Quick Start

Run the gauntlet on the specified pull request number to drive the PR through the full gardening state machine until it is ready for review.

Frequently Asked Questions about pr-creation-flow

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

FAQPage Schema
How do I automate the pull request lifecycle from draft to review?

Automating the pull request lifecycle involves orchestrating build, test, review, and un-drafting stages through a shell-based state machine. This skill manages the entire chain automatically, moving PRs to a maintainer's queue once all criteria are met without manual intervention.

What is a shell-based state machine for pull request gardening?

A shell-based state machine for pull request gardening is a deterministic process that tracks PR stages locally. It uses markers and branch-tracking to enforce draft-discipline across concurrent agentic tasks, ensuring every PR is properly built and tested before review.

How do I prevent duplicate PRs when running concurrent agentic tasks?

To prevent duplicate PRs during concurrent agentic tasks, the workflow uses idempotent job handling. It applies markers and branch-tracking to handle re-claimed jobs safely, ensuring that the same pull request is not created or processed multiple times.

Do I need the GitHub CLI to automate pull request workflows?

Yes, you need the GitHub CLI to automate pull request workflows with this process. It requires integration with GitHub CLI and local shell execution to maintain idempotence and manage the end-to-end PR lifecycle effectively.

How are code and design panel reviews routed for automated pull requests?

Code and design panel reviews are routed by automatically detecting the PR's file surface. The state machine routes the changes to the appropriate code or design panels based on the modified files before un-drafting the pull request for the maintainer.