draft-pr
Skill0 starsChanged 4 months agoMITView on GitHub
Create a draft pull request for the current branch. Use when the user asks to open, create, publish, or draft a PR; mirrors the user's latest repo PR when possible, pushes the branch when needed, runs `gh pr create --draft`, and reports the created PR URL.
- Commits and pushes
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 repository5 other files it gives its agents.
- commitSkill
- distill-chatsSkill
- go-best-practicesSkill
- rust-best-practicesSkill
- second-opinionSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create a real draft PR for the current branch.
- Very specific: line 22
Create the PR with gh pr create --draft --base <base_branch> --head <current_branch> --title "<title>" --body-file <body_file>.
- Distinctive: line 25
Follow repo guidance for command prefixes and validation.
- Distinctive: line 29
Keep it short and specific.
- Distinctive: line 30
Prefer "what" over "how"; avoid vague titles.
- Distinctive: line 35
Prefer the newest PR opened by the current user in this repo as the reference.
- Distinctive: line 42
If no reference PR exists, use the repository's existing PR template when present.
“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
Create a real draft PR for the current branch.
Workflow
- Confirm the current directory is a git repository and identify the current branch.
- Choose the base branch. Use the one the user specified. Otherwise, infer the branch the current branch was created from using the conversation context. If the base is ambiguous, stop and ask the user which base branch to use.
- Inspect the branch diff against the base:
git diff origin/<base_branch>...HEAD --name-statusgit diff origin/<base_branch>...HEAD --statgit diff origin/<base_branch>...HEAD
- Fetch the newest PR opened by the current user in this repo:
gh pr list --state all --author "@me" --limit 1 --json number,title,body,url,createdAt
- Generate the PR title and body from the branch diff. When a latest PR exists, mirror its title style, body structure, scope, and tone as described in PR Body.
- Push the current branch if the remote head does not already exist or is behind local
HEAD. - Create the PR with
gh pr create --draft --base <base_branch> --head <current_branch> --title "<title>" --body-file <body_file>. - Report the created draft PR URL, title, base, head, and any push performed.
Follow repo guidance for command prefixes and validation. Do not create a ready-for-review PR, merge, approve, request review, add labels, or push unrelated branches unless the latest user request explicitly asks.
PR Title
- Keep it short and specific; aim to fit comfortably in GitHub UI.
- Prefer "what" over "how"; avoid vague titles.
- Use imperative mood.
PR Body
Prefer the newest PR opened by the current user in this repo as the reference. Treat it as a template to match closely, not loose inspiration:
- Structure: use the same sections and headings, in the same order, with the same Markdown elements (prose, bullets, checklists, code blocks, links). Do not add sections it lacks, such as "Testing" or "Files changed". If a reference section does not apply to this change, drop it instead of filling it with filler.
- Scope: match its length and level of detail. If it summarizes the change in a few high-level bullets, do the same instead of listing every file or function. If it goes into detail, go into similar detail.
- Title: follow its title conventions, such as ticket prefixes, conventional-commit types, or capitalization.
- Tone: match its voice and wording style.
- Content: write it from the current diff only. Never copy facts, links, or ticket IDs from the reference unless they also apply to this change.
If no reference PR exists, use the repository's existing PR template when present. Otherwise, include:
- Why: 1-2 sentences explaining the problem being solved or the feature being added.
- What: concise description of the new behaviour or functionality introduced.
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.