CC recent update just added a lot of good stuff. I’d open a PR, ask ‘review this code’ and get useless generic stuff like ‘consider adding error handling.’ Thanks Claude, very helpful. Turns out I was using it completely wrong. So here is my fresh take and what I learn. I stopped asking for ‘reviews’ Well this was my problem. ‘Review this PR’ is way too vague. Claude doesn’t know what you actually care about. Now I ask stuff like: This touches our auth flow. Walk through the token refresh logic and any scenario where a user ends up with an expired token? and I get a completely different responses. Claude actually traces through the logic instead of throwing generic suggestions at you. Make it think before suggesting Same trick from debugging >> tell Claude to understand first, suggest later. ‘Read this diff. Don’t suggest changes yet. Just explain what it does and flag anything risky.’ Last week, this caught a refactor that changed the order of two database calls. Would’ve caused an inconsistent state during failures. I was about to approve it. One console hack that nobody is talking about Claude for Chrome can read your browser console. So for frontend PRs, I run the branch locally and ask: ‘Check the console. Anything weird?’ Catches React warnings, failed requests, deprecation notices… all the stuff that technically works but is quietly broken. Where it’s actually useful: Auth/security logic: Claude’s paranoid, catches edge cases Database stuff: N+1 queries, missing indexes, transaction issues ‘Does this fix actually work?’: give it the bug + the fix, it’ll find gaps Where it’s not: Styling opinions: just noise, use a linter Huge PRs: 50+ files, and Claude loses the thread Framework-specific stuff: sometimes suggests ‘cleaner’ code that breaks conventions My workflow now: PR comes in then quick skim then ask Claude a specific question about the riskiest part and ‘explain first, don’t suggest yet’ and dig deeper if it flags something. For anything touching auth or payments, I also run it through CodeRabbit for automated scanning. So yeah, AI reviewing AI code. Kinda meta but this combo catches stuff neither finds alone. Prompt I actually use: This PR [what it does]. Does it accomplish the goal? Edge cases that could break? Subtle behavior changes? Don’t suggest improvements unless something’s actually wrong. That’s it. Extensions are actually solid once you stop treating them like a magic ‘review my code’ button. What else are you people using it for? submitted by /u/thewritingwallah
Originally posted by u/thewritingwallah on r/ClaudeCode
You must log in or # to comment.