write-pr-prose
Skill261 starsChanged 49 days agoApache-2.0View on GitHub
Write or amend the description of an existing PR, and its title only when the request explicitly asks for a title or the PR has none. Use whenever updating PR prose, including after pushing new commits to a branch with an open PR.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- pre-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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 11
Write the description following AGENTS.md's "PR description template" section and .github/pull_request_template.md.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
You are writing the description, and sometimes the title, for a PR: the one for the current checked-out branch, or one the user names. PR titles and descriptions in this repository are authored through this skill so that the model pinned in its frontmatter writes them; context: fork scopes the pin to exactly this work (a bare model: pin is turn-scoped and would leak into the rest of the turn or lapse on the next prompt). The pinned model is a deliberate choice (Jeremy, 2026-08-20) — do not bump it without user permission.
- Run
.claude/skills/write-pr-prose/gather_pr_context.sh [<pr-number>](defaults to the current branch's PR). It prints the existing title and description, the PR discussion (issue comments, reviews, and inline review comments), and the full diff from the PR's base branch — so a stacked PR is described against its own base, not main. The script requires an existing PR; if it exits with an error (no PR found, or the diff could not be retrieved), stop and report the failure instead of writing prose. Read all of it: the existing prose and the comments often carry intent the diff alone does not, and the title and description must reflect the whole change from the PR's base per the guidance in AGENTS.md, not just the recent commits. - Write the description following AGENTS.md's "PR description template" section and
.github/pull_request_template.md. Keep the template's checklist lines rather than deleting them: tick only items actually done, and leave inapplicable items unchecked with a brief in-place reason. - Leave the existing title alone unless the request explicitly asks for a title or the PR has none. "Explicitly asks" means the request names the title: "retitle", "change the title", "the title should be ...", or supplies title wording. Requests to update, amend, rewrite or shorten the description, or to "update the PR" after new commits, are not requests to change the title, even when the description changes substantially. Reviewers track a PR by its title, so renaming it mid-review is churn, not an improvement.
- Apply with
gh pr edit <number> --body-file <file>, adding--titleonly in the cases above.
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.

