draft-pr
Skill0 starsChanged 53 days agoMITView on GitHub
Create a draft PR for the current branch. Use when asked to draft, create, open, or prepare a PR, or to write a PR description.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- flavio-portela/skillstheir own version, first seen Nov 1, 2026
- matheusPavaneli/workbenchtheir own version, first seen Oct 20, 2026
- gigio1023/agent-skillstheir own version, first seen Oct 13, 2026
- gigio1023/gigio-skillstheir own version, first seen Oct 13, 2026
- arklexai/arksimtheir own version, first seen Oct 8, 2026
- wordpress-mobile/WordPress-Androidtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use interview and frontend-design.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dazuckSkillinterview
Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- wordpress-mobile/WordPress-Android★ 3.2ksame name
- ComplianceAsCode/content★ 2.8ksame name
- multigres/multigres★ 2.7ksame name
- microsoft/roosterjs★ 1.3ksame name
- arklexai/arksim★ 234same name
- g2i-ai/agents★ 52same name
- gigio1023/agent-skills★ 2same name
- gigio1023/gigio-skills★ 2same name
- zahardev/aicontext★ 2same name
- k3forx/skills★ 1same name
4 more not listed
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 repository26 other files it gives its agents.
- ask-mattSkill
- code-reviewSkill
- create-prSkill
- ready-prSkill
- developSkill
- self-review-docsSkill
- implement-reviewSkill
- implementSkill
- implement-specSkill
- librarianSkill
- nemesisSkill
- refactorSkill
- research-codebaseSkill
- researchSkill
- review-docsSkill
- self-reviewSkill
- simplifySkill
- tddSkill
- test-auditSkill
- waterfall-challengeSkill
- waterfall-designSkill
- waterfall-implementSkill
- waterfall-planSkill
- waterfall-refactorSkill
- waterfall-reviewSkill
- zero-tech-debtSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Write the context: what prompted the change (a ticket, a thread, a conversation, an incident), constraints agreed outside the repository, …
“Common” is measured: kept by at least 6 in 10 of the 13 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
Draft PR
A fresh subagent writes the description. It reads the branch cold, which is what keeps the body short; the main session supplies only what the repository cannot say.
- Identify the current branch and an appropriate base branch.
- Write the context: what prompted the change (a ticket, a thread, a conversation, an incident), constraints agreed outside the repository, where the PR sits in a stack, and whether it opens as a draft or ready for review. Facts only, never a body: the drafter writes the prose.
- Spawn a subagent. Pass it DRAFTER_BRIEF.md as its persona and DRAFTER_REPORT_FORMAT.md as its output specification, with the branch, the base, and the context as its input.
- Relay the URL. Verify each claim the report marks as inferred and
correct a wrong one with
gh pr edit, that sentence only. If the report says the PR was not created, hand the user its title, body, and command.
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.