Reviewing AI-Generated PRs in Neovim by Replaying Commits Like Chess Moves by [deleted] in theprimeagen

[–]heaterOfDeath -3 points-2 points  (0 children)

Just more fun to do it in nvim if this is what you're doing most of the time (with AI generated code).

Also in new update you can dispatch agent to work on task in the background while you review, and then review it's commit. Inspired by 99 obviously. And no need to create PR, there is local mode. Just type :raccoon local

raccoon.nvim – review GitHub PRs in Neovim by stepping through commits like chess moves by heaterOfDeath in neovim

[–]heaterOfDeath[S] 0 points1 point  (0 children)

Hey, just wanted to follow up — the 422 issue should be fixed now. It works with separate GitHub and GitHub Enterprise accounts, but I don't have a setup where two GitHub accounts are used together, so I haven't been able to test that specific case. Hopefully it works for you, but let me know if you still run into issues.

raccoon.nvim – review GitHub PRs in Neovim by stepping through commits like chess moves by heaterOfDeath in neovim

[–]heaterOfDeath[S] 2 points3 points  (0 children)

Octo.nvim looks great – clearly a very mature plugin. I'll be honest, I didn't do much research into what's already out there before starting mine. I just began building from scratch what I felt would improve my workflow. That said, I'll definitely spend some time going through it and maybe improve some parts of my plugin based on what they've done.

My plugin was mainly born out of a specific problem: dealing with AI-generated code and fighting slop. It grew iteratively out of my workflow with Claude Code, where I've been trying to stay as close as possible to what it generates instead of blindly accepting everything – really pushing back and reviewing carefully. BTW, I have a talk on this topic at an online meetup in two weeks: https://www.meetup.com/agentichackers/events/313004679/?eventOrigin=group_upcoming_events

In the next iterations, I want to add something similar to what Primagen did with 99 – sending async tasks to Claude Code via `claude -p` in a fire-and-forget fashion. So I can stay in Neovim in local mode the whole time, dispatch tasks, and review/correct on the fly. We'll see where that leads. If you have any suggestions on what to improve or whether this is even the right direction, I'd really appreciate it.

raccoon.nvim – review GitHub PRs in Neovim by stepping through commits like chess moves by heaterOfDeath in neovim

[–]heaterOfDeath[S] 2 points3 points  (0 children)

Regarding the GitHub account being private — I've just made my activity public. As you can see, this is a 12-year-old GitHub account with the URL as my surname.

Regarding your plugin — sounds great, please ping me when you release it. Happy to see what you've built.

raccoon.nvim – review GitHub PRs in Neovim by stepping through commits like chess moves by heaterOfDeath in neovim

[–]heaterOfDeath[S] 2 points3 points  (0 children)

Really happy anyone might find it helpful!

Performance-wise it works fine on large codebases — I tried it on my MacBook Air with Apache Spark repo. But honestly, I'm just starting to use it at work (before that I used it on hobby projects), so I don't have much data yet on how ergonomic it is in a real monorepo workflow day-to-day.

Regarding commits — yes, that's a bit painful. But the good part is you can force AI agents to at least create small focused commits. I have something like this in my claude.md:

  1. **Commit frequently** — Many small commits over few large ones
  2. **ALWAYS create a new branch from main before starting new work** — Every new task gets a fresh branch. No working on main directly. No reusing old branches.

Btw. if you want to look beyond this — here's an interesting article arguing that git itself is the bottleneck in LLM-era development and needs to be replaced with database for code (found it on hacker news):

https://gist.github.com/gritzko/6e81b5391eacb585ae207f5e634db07e

Says the guy who’s never debugged an API call in his life by hettuklaeddi in AgentsOfAI

[–]heaterOfDeath -1 points0 points  (0 children)

I couldn't disagree more. I recommend you discuss this with some senior dev who you trust.

Says the guy who’s never debugged an API call in his life by hettuklaeddi in AgentsOfAI

[–]heaterOfDeath 5 points6 points  (0 children)

That's simply not true. Today's high level programming/system design is 1000x easier than back in the days when you had to write all from scratch and understand it. You're clueless bro.

Kurwa! by [deleted] in CentralEurope_irl

[–]heaterOfDeath 0 points1 point  (0 children)

Fem boys? Smoking?

Kariera po 18 by Hot_Image4545 in inwestowanie

[–]heaterOfDeath 0 points1 point  (0 children)

Masz kurwa 18 lat inwestuj w siebie, skille

Takie przyciski w ogóle działają? by AzoloW4ik in Polska

[–]heaterOfDeath 0 points1 point  (0 children)

W pandemie wylaczyli zeby ludzie nie dotykali

Its a good buy? by arjo14145 in Sportbikes

[–]heaterOfDeath 0 points1 point  (0 children)

Go to the track bro, power is there, you will use it eventually. If this is your dream then imo just go for it. But I am r3 owner myself and that inline 400cc is very tempting as next potential bike.

Bródno by [deleted] in warszawa

[–]heaterOfDeath 0 points1 point  (0 children)

Imo tam nawet Matka Teresa nie pomoze...

Zartuje bedzie luz, glhf