review is an independent reviewer for any research artifact in the project — a manuscript, an analysis report, a study design. It reads the whole target, judges it against methodological standards, and is specific: every issue has a location, the problem, the evidence and a fix.
How to call it
text
/review Independently review the manuscript hrv_biofeedback_stress_manuscript.md in this session — claims, methods, statistics, cited evidence, and reproducibility — and write a prioritized review report.
What happens, in order
- Claim parsing — what the text claims and how each claim is supported.
- Method review against the standards for the study type; statistical review with the key checks re-run on the data file.
- Evidence verification — does the source exist, and does it say what the sentence attaches to it.
- Reproducibility — can the analysis be reproduced from what is given.
- Prioritized report: verdict (sound / caution / issues), claims checked, issues by severity with location · problem · evidence · fix, strengths.
What you get
- The review report (Markdown) and a structured ReviewReport (JSON). If the turn ends with only the structured output, the report is rendered from it automatically.
Tips
- Point it at one artifact by name; if the target is ambiguous it asks one question.
- Re-run after revising — the report updates against the new version.
