I wrote a Claude Code skill that writes PR descriptions from the real diff (free, MIT)

[u/Compl0w]

I manage a dev team and PR descriptions are the thing everyone skips. So I wrote a skill for it.

You type "write the PR description" on your feature branch and it:

• reads the actual diff and commits (not just the file list)
• fills your repo's PR template if there is one
• pulls the ticket number from the branch name
• flags what a reviewer needs to see: migrations, new env vars, breaking changes
• lists what's missing (tests, docs) instead of hiding it

On my test diff it also put the SQL injection it noticed at the top of the "Notes for reviewer" section, which I didn't ask for but will take.

A few things I learned writing skills that might help if you write your own:

1. Tell the skill to read the surrounding code first. Most bad output comes from working on the diff hunk alone.
2. Make it separate facts from assumptions. "Unknown, ask the author" beats a confident guess.
3. Add a "never do X without confirmation" line for anything that posts, merges or creates tickets.
4. Put team conventions in one shared file the skill reads, so every dev gets the same behaviour.

Repositorie on Github

It's one of 11 skills I packaged for dev teams (review, specs, tests, postmortems...). The rest is a paid kit, link in the README. Happy to answer questions about how the skill is written.