> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assert.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Comments
> Leaving comments and suggestions, and reviewing alongside your team
Select the lines you want to talk about and press ⌘K. Comments
take markdown, including fenced code blocks.
| Action | Shortcut |
| :-------------------------------- | :-------------------------------------------------------------------------- |
| Add comment | ⌘K |
| Add suggestion | ⌘I |
| Save | ⌘↵ |
| Cancel | esc |
| Delete | ⌫ |
| Widen / narrow the anchored range | ⌃⌥← / ⌃⌥→ |
| Next / previous comment | ] → C / \[ → C |
The comments panel in the left sidebar lists every thread on the pull request with
counts and resolve controls. Resolution state is shared with GitHub.
## Suggestions
Press ⌘I to attach a concrete edit to a comment. You get an
editor seeded with the selected lines, and the author can take your replacement
directly.
## Assert's suggested comments
Assert proposes review comments of its own. Press A to accept one and it
becomes a pending comment of yours, which you can edit before submitting. Accepting
adds a comment; it does not touch the code.
## Rebasing comments
Agents rewrite history constantly, so a comment you drafted against one commit can
end up pointing at code that has moved. When that happens, Assert flags it in the
header with a count of outdated comments.
Click the flag to rebase them onto the latest commit. Assert reports anything it could
not place cleanly as a conflicting comment, and you choose where those land.
## Reviewing with your team
Avatars in the header show who else is in the review. Check them before you start and
you will not duplicate a teammate's pass. You can also request reviewers from Assert,
and the request lands on GitHub.
## Sending comments to an agent
Select the threads you want acted on and send them to Claude, Cursor, or Devin. See
[Agents](/integrations/agents).