/code-review outputs a raw JSON array instead of readable findings

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.