pr-description-writer
Skill0 starsChanged 7 months agoMITView on GitHub
Writes structured pull request descriptions from a diff, branch name, commit list, or plain-English summary. Use this skill when the user asks for a PR description, says "write the PR for this", needs a merge request body, or wants a summary suitable for GitHub/GitLab/Bitbucket pull requests.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- jaskirat1616/grok-skillstheir own version, first seen Nov 1, 2026
- Lethe044/agentskill-kittheir own version, first seen Nov 1, 2026
- Infomaniak/desktop-kDrivetheir own version, first seen Oct 8, 2026
- poorvith-mp/skills-developertheir own version, first seen Aug 19, 2026
- michaelm7456/claude-skillstheir own version, first seen Jul 19, 2026
- ATOM00blue/agent-skills-protheir own version, first seen May 22, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Infomaniak/desktop-kDrive★ 121same name
- Lethe044/agentskill-kit★ 48same name
- jaskirat1616/grok-skills★ 22same name
- ATOM00blue/agent-skills-pro★ 0same name
- michaelm7456/claude-skills★ 0same name
- poorvith-mp/skills-developer★ 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 repository14 other files it gives its agents.
- api-designerSkill
- bug-report-formatterSkill
- changelog-writerSkill
- code-reviewerSkill
- commit-message-writerSkill
- dependency-upgraderSkill
- dockerfile-doctorSkill
- env-var-auditorSkill
- error-message-improverSkill
- migration-plannerSkill
- readme-generatorSkill
- regex-builderSkill
- sql-query-expertSkill
- test-generatorSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
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 47
If the diff implies a breaking change, surface it prominently.
- Distinctive: line 50
If given only a branch name or vague description, ask for the diff or commit list rather than inventing content.
“Common” is measured: kept by at least 6 in 10 of the 5 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
PR Description Writer
You produce pull request descriptions that reviewers actually want to read.
Default template
## Summary
<2–4 sentence plain-English summary of what this PR does and why>
## Changes
- <bullet per logical change, grouped by area>
## How to test
1. <reproducible step>
2. <expected result>
## Screenshots / recordings
<placeholder if UI changes, otherwise omit>
## Risk & rollout
<callouts: feature flag, migration, breaking change, perf, security>
## Related
Closes #<id> · Refs #<id>Rules
- Summary first. A reviewer should understand the PR from the first paragraph alone.
- Group changes by file area or feature, not by file path. Don't list every changed file.
- Always include "How to test" unless the PR is purely internal refactor with full test coverage — then say so explicitly.
- Call out risk for: DB migrations, breaking API changes, new env vars, new dependencies, perf-sensitive paths, security-sensitive code.
- Omit empty sections rather than leaving "N/A".
- Match the project's style if the user provides examples of past PRs.
Process
- Identify the type of change (feature, fix, refactor, infra).
- Extract the user-visible impact, not just code mechanics.
- Draft summary → changes → test steps → risk.
- If the diff implies a breaking change, surface it prominently.
- Output the full markdown, ready to paste into the PR body.
If given only a branch name or vague description, ask for the diff or commit list rather than inventing content.
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.