pr-writing
Installation
SKILL.md
PR writing
A reviewer spends most of their time picturing what the author already saw: the page they opened, the command they ran, the test that went green. Put that in the description. Prose that describes a change is a claim, not evidence.
This skill covers the description only. Prepare it, show it to the user, and wait for their go-ahead before opening or editing the pull request, unless they've told you otherwise.
1. Say who did what
When an AI agent wrote the change, start the description with one line that tells the reviewer how much a human is behind it. Ask the user for their handle. Use gh api user -q .login only after confirming that the signed-in GitHub account is theirs, not a bot or a shared account.
| What the user did | First line |
|---|---|
| Gave the task and approved the approach | > Written by an AI agent on behalf of @handle. @handle has not reviewed it yet. |
| Wrote a spec (an issue, a doc, a plan) that you implemented | > Written by an AI agent on behalf of @handle, following their spec. @handle has not reviewed it yet. |
| Worked out the design with you: the architecture, the API, the trade-offs | > Written by an AI agent on behalf of @handle, who shaped the solution. @handle has not reviewed it yet. |