News for hackers. Stuff that matters.
Re:Cursor CLI by stavros on Thursday August 07, 2025 @06:24PM (#44831145)
I don't really need an IDE, but I do need a great code review interface.
Re:Cursor CLI by Xenoamorphous on Thursday August 07, 2025 @06:36PM (#44831247)
As someone who hasn’t used Claude Code yet, can’t you configure it somehow to use a different tool of your liking, or it has to be in the cli?
Re:Cursor CLI by stavros on Thursday August 07, 2025 @07:27PM (#44831661)
I end up using the VCS tooling (lazygit for me), but coding agents really need to be integrated with this review environment. We need an extra step where the agent will group its changes into logical units (database models in one commit, types in another, business logic in another, tests in another), rather than having to review per-file.

Programming has changed from writing code to reviewing/QAing and reprompting, but the tooling hasn't yet caught up with that workflow. We need Gerrit for coding agents, basically.

Re:Cursor CLI by fooster on Friday August 08, 2025 @12:39AM (#44833467)
I just merge the change and review the diff. If it’s wrong I either revert or ask Claude to fix it.
Re:Cursor CLI by Touche on Thursday August 07, 2025 @10:37PM (#44832831)
I use lazygit for that. But any diff tool you like will work.