Leave line comments
Draft GitHub-style line comments from the overlay while you walk the plan. Comments stay local until you submit a review.
You need GitHub connected only when you submit — drafting works either way. Shortcut reference: Keyboard shortcuts → Comment mode.
Enter comment mode
On a unit that has selectable diff lines:
- Press
c, or use the comment affordance in the overlay. - The UI switches to comment mode: arrow keys move a line cursor on the current unit’s hunks instead of only scrolling the pane.
- 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 or empty context), comment mode has nothing to attach to. How units map to real hunks: How a review plan works.
Select lines
| Action | How |
|---|---|
| Move the cursor | ↑ / ↓ |
| Multi-line range | Hold ⇧ and press ↑ / ↓ |
| Open composer | Enter on the selection |
Selection is limited to lines the extension can map to a GitHub review comment on the current diff. Context-only lines may not all be selectable. Full chord list: Keyboard shortcuts.
Write a draft
- With lines selected, press
Enterto open the composer under that range. - Write the comment body. Markdown is supported (same idea as github.com).
- Save with
⌘/Ctrl+Enter, or cancel withEsc.
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+Enteror cancel withEsc. - Remove — drop that draft without posting.
You can keep walking units and add more drafts before submitting once.
What gets posted
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.
Tip. Prefer commenting as you go unit by unit, then submit once. That matches how GitHub review drafts work: one review, many line comments.
Next. Submit a review · Connect GitHub · Keyboard shortcuts