prlisted

# Create Pull Request - `/pr` — draft PR for the current diff from trunk - `/pr [revision]` — draft PR for that revision - `/pr [revision] ready` — ready for review rather than draft ## Push and get the bookmark The command depends on what the revision already has: ```bash jj git push --bookmark <name> # remote-tracked bookmark jj bookmark track <name>@origin && jj git push --bookmark <name> # local-only bookmark jj git push -c <revision> # no bookmark: creates one ``` Take the bookmark name from the output. ## Review the whole changeset ```bash jj log -r 'trunk()..<bookmark>' # commits going in jj diff --from trunk() --to <bookmark> --stat # everything changing ``` A PR is easier to review as several focused commits than one large one. If the changeset is mixed, reorganize with `jj split` or `jj squash` before opening it. Check `.github/` for a PR template and follow it if one exists. ## Draft the title and body The title summarizes the whole changeset, not just the most recent commit. The body explains why the change was made and what it affects — context and motivation, not implementation. Don't restate what the diff already shows: "added function X" and "modified file Y" earn their place only when the reasoning behind them isn't obvious. Cover user-facing impact, architectural decisions, and trade-offs, following whatever conventions the repository already uses. Tw