proofread

# Academic Proofreading **Report-only skill.** Never edit source files — produce `reviews/<scope>/proofread/<YYYY-MM-DD-HHMM>.md` only (where `<scope>` is the paper slug, e.g. `paper-jtp`). ## Output Path Per `rules/review-artefact-routing.md` (auto-loads in research projects (path-scoped to `paper-*/` and `paper/`)): - **Source slug:** `proofread` - **Write reports to:** `reviews/<scope>/proofread/YYYY-MM-DD.md` inside the project, where `<scope>` is the paper slug (e.g., `paper-jtp`). Path is relative to the research project root, not the Task-Management repo. - **Never** at project root (`./CRITIC-REPORT.md`-style filenames are forbidden — pre-rule layout). - **Idempotency:** if today's file exists, append a same-day descriptor (`{date}-revision.md`, `{date}-r2.md`, `{date}-pre-submission.md`) — never overwrite. - **Index update:** if `reviews/INDEX.md` exists, write a one-line entry under "Latest per source" pointing at the new file. Otherwise `review-recap` will rebuild the index next time it runs. - **Infrastructure repos** (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there. ## When to Use - Before sending a draft to supervisors - Before submission to a journal/conference - After major revisions to check consistency - When you want a fresh-eyes check on writing quality ## When NOT to Use - **Formal audits** — use the Referee 2 agent for systematic verification - **Argument quality** — use `devils-advoca...