style-reviewlisted

# style-review Slow, thorough LLM-assisted prose review. Catches what `/style-check` can't: long/complex sentences, buried verbs, weak topic sentences, hedging in main claims, paragraph-coherence drift, voice inconsistency, and formal/informal pairing failures. Use this for prose that matters: paper drafts, chapters, important emails, externally-visible blog posts. Don't use it on routine project docs or working drafts — overkill. ## How to invoke | Form | What it does | |------|--------------| | `/style-review <file>` | Full review. Mechanical linter first, then LLM. Numbered findings; ask which to apply. | | `/style-review <file> --section <name>` | Restrict the LLM review to one section (intro, abstract, results, etc.). | | `/style-review <file> --no-fix` | Review only, no edit prompts. | ## Workflow ### 1. Run the mechanical linter Always start with the deterministic linter: ```bash python3 ~/research/research-kit/tools/style_lint.py <file> --format json --severity warning ``` If any warning-or-higher violations exist, offer to fix them before the LLM review. No point reviewing prose the linter would re-flag anyway. ### 2. Resolve section structure Identify which sections the file contains so the right per-type guides get loaded. Detection order: 1. **`section_deps.json`** — if the project has `build/paper/section_deps.json`, read it. Each entry has a `type` field per the convention in [`research-kit/rules/section_labels.md`](../../rules/section_label