claude-code - 💡(How to fix) Fix /code-review outputs a raw JSON array instead of readable findings

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Version: 2.1.153 (Claude Code)

The built-in /code-review skill (the multi-angle recall variant, invoked e.g. /code-review high on PR <n>) ends its injected instructions with "Return findings as a JSON array of at most 10 objects." The model therefore prints a raw JSON block as the final user-facing output.

Expected: human-readable, severity-ranked findings (file:line, summary, fix) — the same shape the code-review:code-review plugin command already produces (### Code review / Found N issues...).

Impact: the JSON block is the actual deliverable the user reads, and it's hard to scan in a terminal. Recurring friction.

Suggested fix: change the final "Output" step to request a readable markdown list. The JSON can stay an internal intermediate between the verify phase and the final render.

Repro: run /code-review high on PR <number> in any repo.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING