pr-writer
Skill280 starsChanged 7 days agoGPL-2.0View on GitHub
Writes clear, punchy, human-oriented PR descriptions that focus on what matters. Use this skill whenever a PR title or body is about to be written, including when opening a PR is one step of a larger request. That covers explicit asks ("write a PR description", "draft the PR", "describe this PR", "what should the PR say", "rewrite the PR body", "summarize this branch for review") AND workflow asks that end in a PR ("open a PR", "create the PR", "make a PR", "commit, push and PR", "ship it as a PR", "update the PR description"), and any time you are about to run `gh pr create` or `gh pr edit --body`. Load it before writing the body, even if the user doesn't say "skill" explicitly. Follows the repo's PULL_REQUEST_TEMPLATE when present, otherwise a What it does / Rationale / Implementation / Testing instructions structure.
- Reads credentials
- Commits and pushes
9 other projects use a version of this.
Adopted by
Most recently taken up by
- oxc-project/oxctheir own version, first seen Nov 15, 2026
- strands-agents/harness-sdktheir own version, first seen Oct 14, 2026
- strands-agents/sdk-pythontheir own version, first seen Oct 8, 2026
- TheHiddenDeveloper/jarvis-skillstheir own version, first seen Aug 19, 2026
- getsentry/skillstheir own version, first seen Jul 25, 2026
- kwiggen/claude-code-plugintheir own version, first seen Jul 21, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- oxc-project/oxc★ 23ksame name
- strands-agents/sdk-python★ 9.1ksame name
- strands-agents/harness-sdk★ 8.9ksame name
- getsentry/skills★ 1.2ksame name
- microsoft/SwiftStreamingMarkdown★ 361same name
- tranhieutt/software_development_department★ 71same name
- zebbern/termstack★ 4same name
- kwiggen/claude-code-plugin★ 1same name
- TheHiddenDeveloper/jarvis-skills★ 0same 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- factorySkill
- pixijsSkill
- openstation-extensionSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 12 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 9 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.
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.