pr-description-writer
Skill48 starsChanged 18 days agoMITView on GitHub
Drafts a pull request description with a summary, motivation, a change list, test notes and risks from a diff or commit list. Use when the user opens a pull request, asks for a PR description, or wants reviewers to understand a change quickly.
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
- 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
- kakarot-oncloud/claude-dev-skillstheir own version, first seen Apr 19, 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
- jaskirat1616/grok-skills★ 22same name
- ATOM00blue/agent-skills-pro★ 0same name
- kakarot-oncloud/claude-dev-skills★ 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 repository15 other files it gives its agents.
- api-endpoint-testerSkill
- changelog-generatorSkill
- commit-message-writerSkill
- csv-profilerSkill
- dockerfile-linterSkill
- env-file-auditorSkill
- json-diffSkill
- log-analyzerSkill
- meeting-notes-to-actionsSkill
- python-code-smellsSkill
- readme-doctorSkill
- secure-code-reviewSkill
- skill-authorSkill
- sql-query-reviewerSkill
- todo-extractorSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
5
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 45
Call out anything that needs action at deploy time (new environment variable, migration, feature flag).
- Distinctive: line 46
Keep it under about 300 words unless the change is very large.
- Distinctive: line 47
Do not invent test results.
- Distinctive: line 51
Read the diff and the commit messages and find the main purpose.
- Distinctive: line 58
If the diff is empty or only whitespace, say that there is nothing to describe.
“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
Pull request description writer
When to use
- The user is about to open a pull request and has a diff or a commit list.
- A pull request description is empty or says only "see commits".
- The change is large and reviewers need a reading order.
Template
## Summary
One or two sentences: what changes and why it matters.
## Motivation
The problem or ticket behind this change. Link the issue.
## Changes
- Grouped by area, one line each. Mention renamed or moved files once.
## How it was tested
- Commands run, cases covered, and what was not covered.
## Risks and rollout
- Migrations, config changes, performance effects, how to roll back.
## Review notes
- Where to start reading and what deserves the most attention.Rules
- Lead with the user visible effect, not the file list.
- Be honest about gaps. "Not tested on Windows" helps the reviewer more than silence.
- Call out anything that needs action at deploy time (new environment variable, migration, feature flag).
- Keep it under about 300 words unless the change is very large.
- Do not invent test results. If the user did not say what was tested, ask or write "Not yet tested".
Steps
- Read the diff and the commit messages and find the main purpose.
- Group the changes by area (API, UI, tests, build) instead of by file.
- Fill the template and drop sections that have nothing to say.
- Suggest a title in the form
<type>: <summary>.
Errors
If the diff is empty or only whitespace, say that there is nothing to describe.
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.