Write a pull request description from your changes
For developers who would rather ship than write PR descriptions: turn your branch into a clear pull request description reviewers can act on. Reads the diff and commits, groups the changes by area, and spots what reviewers need to know: migrations, new environment variables, dependency changes, removed exports and pages, UI changes that need screenshots, and linked issues. Asks you only for the why and how to test, then writes the title and description. Opens the PR with gh only if you say so.
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
How this works
- It is a skill: written instructions Claude reads when your request matches what the skill is for. You do not call it by name; just ask for the task.
- While it works, it reads and changes files in the places it lists, nowhere else.
- It runs these commands on your computer: node scripts/pr-facts.mjs, git diff, git log, git merge-base, git rev-parse, git status, gh pr create, gh pr edit.
- It talks to api.github.com over the internet.
- Nothing runs until you choose to use it, and you can remove it any time.
What it can access
What this kit declares, in the same words the CLI shows before you install. On Claude Code the CLI turns these into permission rules, so the agent stops anything undeclared.
Command
Runs the command: node scripts/pr-facts.mjs (with any arguments, without asking)
Command
Runs the command: git diff (with any arguments, without asking)