Feature Request: Add line-by-line code review functionality to file change approvals

[surajpratap]

Description:

Currently, when Claude Code makes changes to a file and presents them for review in the IDE, users can only accept or reject the entire change with a single feedback message. This limits the ability to provide detailed, specific feedback on complex changes.

Feature Request:

Add a PR-like review interface that allows users to:

1. Comment on specific lines: Add a comment button/icon next to each changed line in the diff view
2. Accumulate feedback: Store line-specific comments in memory as the user reviews
3. Batch rejection: When rejecting, automatically aggregate all line comments into a structured feedback string
4. Clear review state: Reset comments after accept/reject actions

Expected Behavior:

Line 15: Use dayjs instead of Date constructor Line 23: Add proper error handling here Line 30: This function should be async Line 45: Missing TypeScript type annotation

This aggregated feedback would be passed to Claude, allowing for comprehensive fixes in a single iteration.

Current Workaround: Users must manually format line-by-line feedback in the rejection message, which is cumbersome and error-prone.

Benefits:

• Improved developer experience
• More efficient code review workflow
• Reduced back-and-forth iterations
• Better alignment with standard PR review practices

Technical Implementation: The plugin would need:

• UI components for line-level commenting
• Local state management for comment storage
• String formatting/aggregation on rejection
• Comment persistence during review session

This feature would significantly enhance the code review experience and bring Claude Code closer to industry-standard review workflows.

[coygeek]

Hey, this is a fantastic idea. I've run into this exact limitation myself and completely agree that a more granular, PR-style review interface for changes would be a massive improvement. Manually typing out feedback like "on line 15, change X to Y" in the single rejection box feels pretty clunky, especially for larger changes.

While we wait for the team to hopefully implement something like this, I've been experimenting with a workaround that might help you out. It uses a combination of two features I found in the docs: IDE selection context and custom slash commands.

According to the IDE integrations docs, "The current selection/tab in the IDE is automatically shared with Claude Code". And the common workflows page shows how to create custom commands that can take arguments.

You can combine these to create a more streamlined feedback loop. Here's how:

1. Create a custom slash command for feedback. Create a file in your project at .claude/commands/feedback.md:

   The user has selected the following code block from your previous suggestion. Please revise your changes based on this specific feedback:
   
   $ARGUMENTS
   

2. Use it in your workflow. When Claude proposes a change in the IDE diff viewer:

   • Instead of accepting/rejecting in the UI, just go back to your editor.
   • Highlight the specific lines you want to comment on.
   • In the Claude Code terminal, use your new command: > /feedback Use dayjs here instead of the native Date constructor

Claude will get the context of the code you selected plus your specific comment, which gets it much closer to the line-by-line feedback you're looking for. You can do this multiple times for different parts of the code.

It's definitely not as smooth as a native UI for line-level comments, but I've found it's a huge step up from trying to describe everything in one big rejection message.

Fingers crossed the team sees this and builds the real thing, but hopefully this helps you in the meantime

[github-actions[bot]]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[bmihaila-bd]

Wanted to reiterate the feature request here as it seems so core to the code review workflow people are used to. With Github/Gitlab or any other platform people are used to comment on any single line in the diff, e.g.

This allows for fine grained feedback to make changes only to a subset of the diff and keep the rest. Current approach is clunky and cumbersome to reject the whole diff that Claude shows and describe which lines are wrong in words. It adds a lot of overhead for the user and also leads to misunderstandings along the way for Claude.

It seems that Googles Antigravity has added this exact feature into the IDE, see

It would be great if Claude's IDE integration /ide would be able to do same and similar then for the Claude code cli to allow editing shown diffs with comments instead of rejecting the whole thing.

[marcindulak]

Linking https://github.com/orgs/community/discussions/9099 Allow PR reviewers to comment on *unchanged* files, since code reviews require an ability to comment on any line in any file in the project, not only to comment on the changed lines in the diff.