Not in an obvious way, but left on its default settings Claude was suggesting -Defensive null checks on non-optional types (hiding real bugs instead of surfacing them) -Manual reformatting instead of just saying “run the linter” -Helper functions extracted from three lines of code that happened to look similar -Backwards-compatibility shims in an internal codebase where we own every callsite So we wrote a SKILL.md that explicitly fights these tendencies (ie: “three similar lines is better than a premature abstraction,” “never rewrite formatting manually, just say run the linter”). We also turned off auto-review on every PR. It was producing too much noise on routine changes. We now trigger it manually on complex diffs. The full skill is here if you want to use it: https://everyrow.io/blog/claude-review-skill Is it crazy to think that the value of AI code review is more about being a forcing function to make us write down our team’s standards that we were never explicit about, rather than actually catching bugs?? submitted by /u/ddp26
Originally posted by u/ddp26 on r/ClaudeCode
You must log in or # to comment.