open-draft-pr
Skill2 starsChanged 4 months agoMITView on GitHub
Open or update a Draft pull request and apply projection labels from pin ⋉ handoff.forge (human walker). Use after content skills such as spec-draft, prd-impact-map, or pre-implement (wave Draft PR) when the user authorizes publish. Orchestrators use ForgeClient on external-action nodes instead — do not auto-invoke this skill.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- fallow-rs/fallowtheir own version, first seen Oct 8, 2026
- ethanaubuchon/dossier-tradecrafttheir own version, first seen Sep 26, 2026
- kvantatech/RedLinetheir own version, first seen Aug 6, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- fallow-rs/fallow★ 5.4ksame name
- ethanaubuchon/dossier-tradecraft★ 3same name
- kvantatech/RedLine★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- ground-specSkill
- initiative-feasibilitySkill
- learning-extractSkill
- loop-specSkill
- pre-implementSkill
- purge-initiative-artifacts-appSkill
- spec-draftSkill
- spec-implementation-planSkill
- spec-technical-reviewSkill
- ensure-repo-graphSkill
- post-product-questionsSkill
- prd-codebase-mapSkill
- review-product-questionsSkill
- commit-workspaceSkill
- create-board-ticketsSkill
- prd-impact-mapSkill
- prd-qualitySkill
- prd-thinkSkill
- purge-initiative-artifacts-metaSkill
- review-findingsSkill
- update-documentsSkill
- validate-requirementsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 26
When you (human) run this skill: explicit user confirmation before mutate (chat yes / UI).
- Very specific: line 44
Ensure branch exists / matches readiness (without inventing policy).
- Distinctive: line 47
Create or update Draft PR (title, body from readiness).
- Very specific: line 54
Never merge. Never apply *-lgtm.
- Very specific: line 63
Not a graph node — resume programme from the content handoff’s next_candidates after successful PR action (human records auth).
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Open Draft PR
Human-walker equivalent of Gateflow ForgeClient open/update Draft PR
(forge.action: open_draft_pr).
NON-NEGOTIABLE
- Require a complete
handoff.forgefrom the content skill (pinrequiresfilled). Incomplete → ask or block; do not invent title/body/labels. - Merge pin policy with handoff: pin wins on
action,draft,apply_labels,remove_labels. actionmust beopen_draft_pr. Open or update a Draft PR whendraft: true.- Apply only projection labels from policy. Never apply
*-lgtm. - When you (human) run this skill: explicit user confirmation before
mutate (chat yes / UI). Content skill recommendation is not authorization
by itself. When the pin sets
authorization: automatedon the matchingexternal-action(spec-pr-action,wave-pr-action), Gateflow ForgeClient may open/update the Draft PR without interactive STOP — that path does not invoke this skill. This skill remains human-confirm. - Tool-neutral Forge tooling (
gh, REST, …) — examples only.
Inputs
- Content-skill handoff with
external_action: trueandforge: - Pin node for the next
external-action(prd-pr-action,spec-pr-action, orwave-pr-action) - Workspace files referenced by
body_path/ artifact
Process
- Validate
handoff.forgeagainst pinrequiresand label policy. - Ensure branch exists / matches readiness (without inventing policy).
For
wave-pr-action, requirehead_refandbase_reffrom the handoff (wave branch → integration base). - Create or update Draft PR (title, body from readiness).
- Apply
apply_labels; removeremove_labels/ obsolete projection labels per pin. Wave Draft PRs typically carry no auto labels from the pin. - Report PR URL; emit forge-step handoff using
references/output-template.md —
artifact.pathisnull(this skill has no workspace artifact); do not invent a note file to hold the result. - Never merge. Never apply
*-lgtm. Wave merge stays human-only atwave-signoff.
Workflow handoff
- Emit the envelope from references/output-template.md
in chat; stage id:
open-draft-pr.artifact.path: null— there is no workspace file to persist for this stage. - Dual-write
handoff_pathwhen bound. - Not a graph node — resume programme from the content handoff’s
next_candidatesafter successful PR action (human records auth).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

