Manage PR

Titles, style, and remote naming follow the git-conventions skill. PRs live on the repo's primary remote; this skill supports GitHub through gh. An explicit repo convention (PR template, title check, contributing doc) wins over these defaults.

Create or update

1. Inspect first: git log <base>..HEAD --oneline, git diff <base>...HEAD --stat, and gh pr view for existing PR state.
2. Title: type(scope): description.
3. Body from the template below through --body-file; pass explicit flags so gh never prompts.
4. Push the branch to the primary remote first (git push -u <primary> <branch>; repos usually have two remotes, and an unset upstream makes gh prompt).
5. Create ready for review and self-assigned: gh pr create --assignee @me --base <base> --title <title> --body-file <file>.
6. Fill Verification only with commands actually run and their results.

Template (omit Notes when empty):

## Summary

- 2-5 plain bullets: what changed and why.
- Stacked on #N. (stacked PRs only)