I really want to like the built-in /code-review skill, but my experience with it has been downright tragic. Here’s exactly how it goes every time: it finds a few valid issues, attempts to fix them, and immediately introduces 5 new bugs. I tried letting it iterate on a review for almost an hour the other day hoping it would eventually stabilize, but it just got stuck in an infinite loop chasing its own tail. What actually does work for me is ignoring the built-in skill entirely. My current workflow: I just finish a chunk of code, create a PR, and then manually prompt CC with something like: “Do a code review on this PR. Focus strictly on anti-patterns and technical debt.” Doing it manually this way yields drastically better results, keeps it focused, and avoids the endless loop of breaking changes. Has anyone actually gotten the official /code-review command to work reliably without it nuking the codebase? What’s your workflow looking like right now? submitted by /u/hnizdja2
Originally posted by u/hnizdja2 on r/ClaudeCode