Team PR — Create the Pull Request
Before each consuming step, read its linked shared rules from this installed skill directory. If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading.
Before finalizing prose you author, read the writing standards; for the PR body, apply its ## One busy reader rule and its ## Self-lint. Preserve exact commands, tokens, and templates.
Two modes:
- Resume mode —
$ARGUMENTS/1-task.mdand$ARGUMENTS/6-design.mdexist. Execution step 3 binds one review status from the newestreview-<n>.mdand one security status from the newestsecurity-review-<n>.md. - Standalone mode — no matching artifact directory, but the working tree has commits or staged changes ready to ship. The current branch is the work source.
Core contracts
Each is detailed in Execution at the step named.
- Update an existing CHANGELOG.md after step 3 binds the review and security statuses, and commit before opening any PR; never create one unrequested (step 6).
- Open a draft PR automatically — do not stop to ask (step 7), then report it and how to mark it ready for review.
- Multi-repo: one draft PR per repo, with
## Companion PRslinks. Tracking rules own the in-review transition and the home-only closing rule. - After each push, refresh the body with exactly one closing line: never duplicated, never dropped (step 10).
- A branch that impacts a UI always carries screenshots (step 4).
- Deferred findings and cross-model dispositions are comments on the home PR, never the body: run review comments after open and after each refresh; a refresh posts only missing comments.
- Subagents and inline work split per Execution
## Step dispatch.
Apply the body authoring rules to initial drafts and every refresh.
Procedure references
Read each reference completely when reaching that stage, in order.
- Input
- Execution
- PR Body Template
- Screenshot Upload
- Changelog Update
- Commit Discipline
- Review Comments
Applied principles
Read and apply: focused work rules.