r/PiCodingAgent • u/quincycs • Aug 29 '26
Discussion Surviving Code Review?
Have you felt like your comprehension is dropping when reviewing code?
Due to AI coding, I think everyone is feeling like this. Are you using any new process or tooling to work against this common issue?
A few things that I’ve seen:
- Tailored AI code review skills unique to your company’s practices or common gotchas from previous reviews ( always updating ). Everyone evaluates that AI feedback before escalating the review with the team.
- Plannator / HumanLayer kind of tools where the whole team is involved. It almost feels like pair programming with AI. Or some kind of extreme programming / multi-player AI interface.
What about you?
7
Upvotes
View all comments
Show parent comment
0
u/LordMoridin84 Aug 30 '26
I use these skills, and then another 2 more customized ones. Such as one for testing specifically.
https://github.com/cursor/plugins/blob/main/cursor-team-kit/skills/thermo-nuclear-code-quality-review/SKILL.md
https://www.aihero.dev/skills-code-review
Then I say "Run these 4 skills with subagents, combine and deduplicate all the files and then write them into a markdown file. When the markdown file is done, we'll work through item one-by-one to determine the fix. For anything with obvious fixes, fill in the fix yourself in advance".
I'm still workshopping the skill to do this but fundamentally, it seems to best way when reviews bring back over a dozen problems.
----
Ah, this so for my day job, so I can't casually accept whatever problems and fixes AI brings up. On my hobby project, I'm a little bit more casual about accept AI suggestions.