pull-requestlisted
Install: claude install-skill birdseyeglobal/portage
# Pull Request Guidelines
This skill owns pull request operating logic, including summary prose. Pair with
`content-styleguide` for deeper revision: clarity, word choice, voice, tone,
and AI-artifact cleanup.
## Communication Contract
A pull request body is addressed first to a specific reader: the reviewer. It is
also a durable review interface that should help future maintainers recover the
author's mental model without turning review into a checklist.
It should communicate:
- what changed;
- why the change exists;
- what context, constraint, or decision shaped it;
- what is settled, uncertain, or intentionally out of scope;
- where risk is concentrated, if that changes how the reviewer should read;
- where reviewer attention is useful;
- what a future maintainer should be able to trace from the PR record.
Keep the pull request body durable. Use comments for live dialogue,
negotiation, open-ended reviewer-role questions, or follow-up coordination.
## Review Posture
Review posture is a review aid, not the core contract. Use it when naming the
kind of attention needed will help the reviewer.
Common postures:
- correctness check;
- design critique;
- boundary review;
- migration review;
- live testing;
- verification;
- QA;
- merge readiness;
- follow-up issue capture.
Suggest the posture without over-controlling the reviewer. If the reviewer may
need to define their own responsibility, invite that in a PR comment rather than
the durable summary.
## Workflow
1. Re