Leave line comments

Draft GitHub-style line comments in Guided Review while you follow the walkthrough. On the Chrome extension, comments stay local until you submit a review. On the CLI, the same comment mode leaves notes in the local session — there is no GitHub submit; use Generate Prompt to copy them for a coding agent instead.

You need GitHub connected only when you submit from the extension — drafting works either way. Shortcut reference: Keyboard shortcuts → Comment mode.

Enter comment mode

On a unit that has selectable diff lines:

1. Press c, or use the comment affordance in Guided Review.
2. The UI switches to comment mode: arrow keys move a line cursor on the current unit’s hunks instead of only scrolling the pane.
3. Press Esc (when the composer is closed) to leave comment mode and return to normal navigation.

If a unit has no selectable lines (for example binary / image or empty context), comment mode has nothing to attach to. How units map to real hunks: How a review plan works.

Select lines

Selection is limited to lines Guided Review can map on the current diff (on the extension, lines that can become a GitHub review comment). Context-only lines may not all be selectable. Full chord list: Keyboard shortcuts.

Write a draft

1. With lines selected, press Enter to open the composer under that range.
2. Write the comment body. Markdown is supported (same idea as github.com).
3. Save with ⌘/Ctrl + Enter, or cancel with Esc.

Drafts appear under the line range as Draft cards. They are stored with the active review session until you submit or discard them — they do not leave the browser until submit (Privacy & data).

Edit or remove drafts

On a draft card:

• Edit — reopen the body, then save with ⌘/Ctrl + Enter or cancel with Esc.
• Remove — drop that draft without posting.

You can keep walking units and add more drafts before submitting once.

What gets posted

Extension: Nothing is sent to GitHub until you open Submit Review and confirm. Then every remaining draft is included as line comments on that review, along with the overall event type and optional summary. Details: Submit a review.

If the PR diff has changed since you drafted (rebase, force-push, new commits), GitHub may reject some line anchors — you’ll see an error on submit (Troubleshooting). Re-open the review, refresh the plan if needed, and re-draft on the current lines.

CLI: Notes never leave your machine via Guided Review. Generate Prompt builds a coding-agent prompt from them and copies it to the clipboard — Generate Prompt.

Next. Submit a review · Generate Prompt · CLI · Keyboard shortcuts