Claude Code /code-review Now Reports Only Bugs, Labels Each Finding by Severity and Ends With a Fix
Claude Code 2.1.328 narrows /code-review on most models so it reports only bugs and CLAUDE.md violations. Each finding is now marked Important, Pre-existing or Nit, and each summary ends with a suggested fix. Reuse, simplification and efficiency cleanups move to /simplify.
Key Takeaways
/code-reviewnow reports only bugs and CLAUDE.md violations on most models, dropping style and cleanup suggestions.- Reuse, simplification and efficiency cleanups move to
/simplify, which becomes the companion command for that work. - Every finding is tagged Important, Pre-existing or Nit, so reviewers can separate merge blockers from background noise.
- Pre-existing marks bugs the change did not introduce, which keeps a reviewer from blaming a pull request for old problems.
- Each summary now ends with a suggested fix, giving the output a clear next step.
- A clean review now reads "Code review found no issues.", removing any ambiguity about an empty result.
A narrower, more trustworthy review
Claude Code 2.1.328 changes what /code-review reports on most models. The command now covers only two things: correctness bugs and violations of the project's CLAUDE.md rules. Suggestions about reuse, simplification and efficiency no longer appear in its output. Developers who want that kind of cleanup pass are pointed to /simplify, which covers it as a separate command.
The split makes each command's output easier to act on. A review that mixes real defects with stylistic suggestions forces the reader to triage before fixing anything. With the cleanup suggestions moved out, a finding from /code-review is more likely to be something that needs to change before merging.
Severity labels on every finding
Each finding is now marked Important, Pre-existing or Nit. Important flags a bug worth fixing before merge. Pre-existing marks a problem that was already in the codebase and was not introduced by the change under review. Nit marks a minor point that should not block anything. Labels let a reviewer decide at a glance which items gate the merge and which can wait for a follow-up.
Summaries that end with a fix
Each review summary now ends with a suggested fix, so the output closes on a next step rather than a list of problems. When a review turns up nothing, the list now reads "Code review found no issues," which makes a clean result unambiguous instead of leaving an empty section.
Scope
The behavior applies on most models, per the release notes. Developers who relied on /code-review to surface simplification ideas should run /simplify alongside it.