[FEATURE] VS Code Plugin: "review mode" for arbitrary files, similar to plan mode for plan files

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Feature request: "review mode" for arbitrary files, similar to plan mode for plan files

In plan mode today, the loop between Claude and the user feels great: Claude writes a plan file, the user can edit it directly, select areas of the file to add comments / questions, and Claude sees those edits on the next turn. It's a shared, editable artifact that both sides can read and write.

I'd like the same loop for code files (and any other files in the workspace), not just plan files. This would basically mimic a pull request review, but directly in the VS Code IDE.

Use case: code review with Claude. After Claude writes a non-trivial chunk of code, I currently must:

1. Open the file in my IDE.
2. Add inline comments like // ?? why this magic number or // rename this or // drop this whole branch.
3. Tell Claude "address my comments in foo.ts".
4. Have Claude pick up everything I wrote, address each comment, edit the file, and clear the markers.

This works informally today (add // CLAUDE: markers, tell Claude to grep), but it's lossy:

• No formal mode means I have to remind Claude to look (the file's contents aren't auto-included in the next turn).
• No convention means each user invents their own marker style.
• No "clear when addressed" workflow means stale markers can pile up.
• Need to add comments at the top of a line, instead of having the ability to select, let's say, a single word to comment on

Proposed Solution

• The possibility to select chunks of text and add comments(same as we can currently do on plan files) then tell Claude to check and address all the comments in the current file(multiple files at the same time would be even better).

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_