pr-pipeline
Plan and build a release or a batch of changes as small PRs, where separate agents implement, test from a clean clone, review adversarially, fix, open the PR, answer review bots and bring it to green CI. A scripted path gate and a merge-safety agent decide which PRs an agent may merge; the maintainer merges the rest, and the main session lands them and runs the release script. Use when the user asks to plan and build a release, a milestone or a set of issues "with the usual workflow", to run waves of PRs through review, or to set up this loop in a new repo. Not for a single quick fix by hand; one issue without a plan goes through the `quick` option of a wave, which triages it first.
Target: Target not categorized. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Agent PR pipeline
- The loop for one PR
- Before the first run in a repo
- Step 1: write the plan, then review the plan
- Step 2: run one wave
- Workflow arguments
- Role agents
- Cost and the prompt cache
One PR at a time is easy to check. Many PRs at once are not, unless each PR goes through the same fixed loop and no agent checks its own work. This skill is that loop. This skill is part of the agent-pr-pipeline plugin. The plugin folder is ${CLAUDEPLUGINROOT}: the scripts, templates and the workflow are there. Each step runs as one of the plugin's role agents (agent-pr-pipeline: , see "Role agents"). Summary: a plan is reviewed first, including whether it still serves the product's goals. A quick fix has no plan: a triager first decides build, plan or decline for the issue, and a build gets the same product-fit check on its entry. Then different agents build, test, review for bugs, review for architecture and (where the plan asks) try each PR like a user until it is clean, or until a person settles an architecture question. A code PR then gets one capped minor pass, kept only when its own check passes. A docs agent then brings the docs in line, and a short round checks its commits. Then the PR is opened and the bots are answered. On the final head, a script checks the PR's files against the gated paths of .github/pipeline.json, and for a PR the gate does not hold a merge-safety ag
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- alfhen/agent-pr-pipeline
- Source file
- skills/pr-pipeline/SKILL.md
- Fixed revision
- 52ec312d3d4ed8f325e4341052e4739f0cb74fdb
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: alfhen/agent-pr-pipeline · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T15:00:17.877Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.