PR description writer
Writes a pull request description from the diff and commits covering what changed and why, how it was tested, risks and rollout, and screenshots for UI, without inventing claims. Use when the user asks for a PR description or is about to open a PR.
pr-description-writerInstall
Run one command — it saves SKILL.md into your agent's skills folder. Restart the agent and the skill is picked up automatically.
mkdir -p ~/.claude/skills/pr-description-writer && curl -fsSL https://anymodel.org/en/skills/git-workflow/pr-description-writer/SKILL.md -o ~/.claude/skills/pr-description-writer/SKILL.md
mkdir -p ~/.agents/skills/pr-description-writer && curl -fsSL https://anymodel.org/en/skills/git-workflow/pr-description-writer/SKILL.md -o ~/.agents/skills/pr-description-writer/SKILL.md
New-Item -ItemType Directory -Force "$HOME\.claude\skills\pr-description-writer" | Out-Null; Invoke-WebRequest https://anymodel.org/en/skills/git-workflow/pr-description-writer/SKILL.md -UseBasicParsing -OutFile "$HOME\.claude\skills\pr-description-writer\SKILL.md"
New-Item -ItemType Directory -Force "$HOME\.agents\skills\pr-description-writer" | Out-Null; Invoke-WebRequest https://anymodel.org/en/skills/git-workflow/pr-description-writer/SKILL.md -UseBasicParsing -OutFile "$HOME\.agents\skills\pr-description-writer\SKILL.md"
Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/git-workflow/pr-description-writer/SKILL.md
SKILL.md
PR Description Writer
A good PR description lets a reviewer understand the change in two minutes and know where to look hardest. Derive it from evidence: the diff, the commits and what you actually ran.
1. Gather the evidence
git fetch origin
git log --format='%h %s%n%b' origin/main..HEAD
git diff origin/main...HEAD --stat
git diff origin/main...HEAD
gh pr view --json title,body,url # if a PR already exists
Also read: the linked issue or ticket, a PR template in .github/pull_request_template.md or docs/, and CONTRIBUTING.md. If the repo has a template, fill in its sections in its order instead of using the structure below.
2. Understand before writing
Answer these for yourself from the diff:
- What problem does this solve, and for whom?
- What is the behavior before and after?
- What are the riskiest hunks (migrations, auth, money, concurrency, public API)?
- What did the author test, and how? Look for new tests and ask the user for anything not visible in the diff (manual checks, environments).
If you cannot answer "why", ask the user one question rather than guessing.
3. Structure
## Why
<the problem or goal, one short paragraph; link the issue>
## What changes
- <behavioral change 1>
- <behavioral change 2>
- <notable implementation decision and the reason>
## How it was tested
- <commands run and their result, e.g. "npm test: 214 passed">
- <manual steps, environment, data used>
## Risks and rollout
- <migration order, new env vars, feature flags, compatibility, performance impact>
- <how to roll back>
## Screenshots
<before / after for UI changes; crop to the relevant area>
## Out of scope
- <related things deliberately not done, follow-ups>
Drop sections that do not apply (no UI means no Screenshots). Keep it short; a three-line fix gets a three-line description.
4. Style rules
- Title: short, imperative, states the change (matches repo convention, e.g. ticket key prefix if they use one).
- Describe behavior and intent, not a file-by-file listing; the diff already lists files.
- Group commits into a story when there are many; do not paste the raw commit log.
- Call out reviewer attention points: "please check the lock ordering in
queue.go". - Note breaking changes and required deploy steps at the top of Risks, in plain words.
- Language: follow the language the team uses in earlier PRs.
5. Truthfulness
- Only claim tests passed if you ran them in this session or the user told you so; otherwise write "not run" or leave the line for the user.
- Do not claim performance gains, security fixes or compatibility you did not verify.
- Do not include secrets, tokens, internal hostnames, personal data or private chat content in text or screenshots. Check images before attaching.
- Reference issues with the closing keyword only if the PR truly completes them (
Closes #123); otherwiseRefs #123.
6. Output
Return the title and the body as text ready to paste. Create or edit the PR only when the user asks:
gh pr create --title "<title>" --body-file pr-body.md
gh pr edit 123 --body-file pr-body.md
Write the body file outside the repository (or delete it afterwards) so it is not committed.
Pitfalls
- Do not leave template placeholders or empty headings in the final text.
- Do not write marketing language ("robust", "seamless"); say what the code does.
- Do not hide risk to make the PR look small; reviewers trust honest descriptions.
- Do not describe commits that are not on the branch, or stale changes after a rebase; re-read the diff.
- Do not push the branch or open the PR without the user's go-ahead.
Source: AnyModel skills catalog · License: CC BY 4.0
Connect through AnyModel API
This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.
AnyModel