pr
Skill20 starsChanged 26 days agoMITView on GitHub
Commits, pushes, and opens a draft pull request whose body a reviewer can scan in under a minute: the problem, how it was solved, why that way. TRIGGER when: the user asks to open a PR, raise a pull request, submit work for review, write a PR body for work that has no PR yet, or says "open a pr", "pr this", "ship this for review". SKIP for: reviewing a PR's code or diff, updating or re-describing a PR that already exists, addressing review comments on a PR, writing a commit message alone, or pushing a branch without opening a PR.
In this repository6 other files it gives its agents.
- create-adrSkill
- create-rfcSkill
- diagnoseSkill
- forgeSkill
- grill-meSkill
- show-meSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
- Very specific: line 30
No verb given, and the branch has commits the base does not: assume open.
- Distinctive: line 36
Every body this skill writes passes both.
- Distinctive: line 39
A reviewer scans it in under 60 seconds: Not reads — scans.
- Distinctive: line 43
Test 2 is decided from the diff before drafting, and test 1 is re-checked against the draft.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PR
One verb per invocation.
Verbs
open is the only verb: commit, push, and open a draft PR with a written body.
Procedure: references/open.md.
No verb given, and the branch has commits the base does not: assume open. A
PR already exists for the branch: stop, give its URL, and say open never
updates an existing PR. Do not infer a verb absent from this file.
The two tests
Every body this skill writes passes both. They are the whole quality bar; there is no word count and no mandatory section.
- A reviewer scans it in under 60 seconds. Not reads — scans.
- The body is never more complex than the fix. A one-line dependency bump cannot earn three paragraphs.
Test 2 is decided from the diff before drafting, and test 1 is re-checked against the draft. Both procedures are in references/writing-the-body.md.
Writing the body
Load references/writing-the-body.md before writing any body. There is no template: sections are not mandatory, not fixed in order, and not named in advance. A change that needs one sentence gets one sentence.
Credits
Framing adapted from Dex Horthy's visual-pr; views come from this repo's
show-me. See CREDITS.md.
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.