review-copylisted

# Copy Review Be thorough but concise. **Use this when:** Reviewing reader-facing content for clarity and orientation - web pages, blog posts, landing pages, quick-start guides, research reports, outreach copy, prototypes. **Don't use this when:** Reviewing code quality (/review-code), testing a running web app (/review-browser), checking usability and accessibility (/review-ux), reviewing command prompts (/review-commands), checking plan completion (/review-plan), or doing a pre-release check (/review-full). **Important:** This skill reviews whether content orients a fresh reader. It does not review usability, accessibility, or interaction design - use `/review-ux` for those. ## Critical Rules <rules> 1. **THE REVIEW PHASE REPORTS ONLY** - Reviewing never edits files; findings are its product. After the report, the same run continues into the auto loop (rule 2), which is what applies fixes 2. **Audit, then auto-fix, with pages** - Copy findings are audited before the report per M2 in `.claude/skills/shared/hitl-loop.md`, so the report shows survivors only plus an Audited out log for the kills. They do not then wait for a human "fix it": after the report, survivors are auto-fixed and re-verified, and each finding exits as page, digest, or log per `.claude/skills/shared/hitl-loop.md` (pages only per M1 - who the real reader is may be a question only the user can answer; saying "report only" keeps a run report-first, M10) 3. **Explain simply** - Use plain English, avoid j