Getting started
Pull requests
Complete PR reads in responsibility 6. Implement submissions, reviews, and merging after deciding source ownership and write direction in responsibility 7. These are targets, not released CLI syntax.
Resolve the target
Resolve repositories explicitly or from the Git remote. Select PRs by number or branch; when omitted, resolve the current branch’s Open/Draft PR. Return candidates when ambiguous rather than guessing a write target.
| Operation | Required behavior |
|---|---|
| list / status / view | Lists, relevant PRs, details, pagination, JSON |
| diff / checks | Patch, filenames only, excluded paths, CI state, watch to completion |
| checkout | Fetch PR branch, local alias, detached HEAD, preserve existing work |
| create / edit / ready | Title, body, base/head, Draft transitions |
| review / comment | Distinguish formal reviews and comments; file or stdin bodies |
| thread | List, unresolved filter, reply, resolve, reopen |
| merge / close / reopen | Protection and Checks, enable/disable auto-merge, state transitions |
| refresh | Recheck change versions from current refs; avoid duplicate updates for identical SHAs |
Pin the reviewed version
Bind diffs, comments, and reviews to a change version or base/head SHAs. Detect approval or merging against stale heads. Return Checks and thread states as JSON for evidence-based agent decisions.
Reference: Cursor PR command specification, inspected September 13, 2026. Use the same APIs and permissions as Forge PR requirements.