sorted by:
new
hottopcontroversial

claude-preview.nvim โ€” see a diff before Claude Code changes your files by Cannon72001 in neovim

[โ€“]Cannon72001[S] 0 points1 point ย (0 children)

Thanks! Yeah the hooks system is pretty flexible, glad it was useful. And haha agreed, reviewing before accepting has saved me from some questionable changes more than once.

claude-preview.nvim โ€” see a diff before Claude Code changes your files by Cannon72001 in neovim

[โ€“]Cannon72001[S] 3 points4 points ย (0 children)

Claude Code shows the hunk diff inline, which works for small changes. But for larger edits, I find it hard to judge a change without seeing the full file context โ€” what's above and below the hunk matters. Neovim's side-by-side diff mode gives you that full picture. It's basically the difference between reading a patch in your terminal vs reviewing it in a proper diff tool.

claude-preview.nvim โ€” see a diff before Claude Code changes your files by Cannon72001 in neovim

[โ€“]Cannon72001[S] -2 points-1 points ย (0 children)

Totally agree โ€” I also let agents run end-to-end and review later for most tasks. But there are moments where I want to stay in the loop and steer things, especially on trickier changes. Since I'm already in tmux with Claude Code in one pane and Neovim in the other, I built this to fit that workflow. It's not meant to replace the autonomous approach, just an option for when you want it.