← All skills · Automation · PR Description Writer

PR Description Writer — finished output
Runs inClaude Code Codex Cursor Muse Dot Grok Bot Cue OpenClaw Hermes
Needs:The change summary: pr.txt (a Title line saying what the PR does, one Change line per change, one Why line per reason, one Test line per check — what ran, then | Result: pass, fail, or not run — and one Risk line per risk — what could go wrong, then | Level: low, medium, or high — plus optional Note lines).

Similar Skills

View all skills →

What you get

  • A structured PR description: Summary, Why, Testing with recorded results, and Risk with a door verdict and blast radius
  • A Readiness verdict — Ready to paste, or Not ready with the gaps and errors named
  • Every test with its recorded result — a test with no result is listed as Not recorded, never assumed passed
  • Every risk with its stated level — a risk with no level is listed as Not stated, never assigned one
  • Every gap, input error, and warning named in the report

Good fit

  • Opening a pull request and giving the reviewer the facts up front
  • Making untested or unrecorded checks visible before merging, instead of hiding them
  • Flagging one-way-door changes — migrations, deletions, breaking changes — before they merge

Not for

  • Approving a change — a description describes it, a reviewer still reads the diff
  • Deciding how risky a change is — the door verdict counts irreversible words, not risk
  • Writing a PR with no change summary — the report will list the gaps, not invent the description

Sample output

An example of what this Skill produces. Sample content, shown for illustration.

Pull request — sample

Changes: 3 | Why: 2 | Tests: 3 (3 passed, 0 failed, 0 not run, 0 not recorded) | Risks: 2 | Gaps: 0 | Errors: 0 | Warnings: 0

Ready to paste — every section is present and the input had no errors.

Summary: 1. Return the cached result when content is unchanged in the save path; 2. Add a GET /sessions/:id/result endpoint that serves the cached result; 3. Show a "Cached" badge on the session page when the result comes from cache.

Testing: Run the save twice with unchanged content — Pass; Open the cached result endpoint for a finished session — Pass; Load the session page for a cached result — Pass.

Door: Two-way door — no irreversible step mentioned; cheap to roll back. Blast radius: api · ui · code.

What this description is not: a description describes the change; it does not approve it — a reviewer still reads the diff.

About this Skill

You say
The cached-save change is ready — write the PR description a reviewer can actually use.

How to install

  1. Copy the install prompt into your agent: Read https://skillu.dev/install/agent.md, then install the PR Description Writer skill (pr-description-writer).
  2. Or download the Skill package from this page after launch and place its folder in your agent’s skills directory.
  3. Call it with a slash command, e.g. /pr-description-writer, and describe what you want in plain words.

FAQ

Does Ready to paste mean the PR is approved?

No. It means every section is present and the input had no errors — the description is complete, not the change. A reviewer still reads the diff, and a failing test in the Testing table is a finding, not a blocker for the description.

What if a test has no recorded result?

It is listed as Not recorded in the Testing table, and the warnings name it. The report never assumes a test passed — a description that hides an unrun test is worse than no description.

Get Premium access Browse more skills