file-pr
Installation
SKILL.md
File PR
A PR has three readers: the person who asked for the change, the reviewer, and whoever ships it to production days later. Write for all three.
Before filing, check whether a PR for this branch already exists, and read the diff against the base branch to confirm it matches the goal you were given. The repo's AGENTS.md (or CLAUDE.md) names who owns which steps, where secrets live, and how reviews run; where it is silent, use roles ("whoever deploys").
Title
Titles usually become commit messages, so follow the repo's conventions: read recently merged PRs and the git log for the shape. Say why the change matters, not what you touched.
- BAD:
perf(server): negotiate permessage-deflate on the websocket - GOOD:
perf(server): cut websocket frame size by 70% with gzipping