Workflow & Best Practices
If user requests complete review, execute in order:
- Format Check → fix critical issues
- Grammar Analysis → fix errors
- De-AI Editing → reduce AI writing traces
- Long Sentence Analysis → simplify complex sentences
- Expression Restructuring → improve academic tone
Best Practices
- Start with Compilation: Verify document compiles before other checks
- Iterative Refinement: Apply one module at a time for better control
- Preserve Protected Elements: Never modify
@cite,@ref,@label, math environments - Verify Before Commit: Review all suggestions before accepting changes
- Use with version control (git) to track changes
Revision Order (logic → sentence → lexical, do not reverse)
When a request needs more than one polish pass, apply changes in this order and do not invert it:
- Argument / logic — paragraph order, missing or duplicated main messages, section transitions.
- Sentence structure — split overly long sentences, passive→active, front-load high-information content.
- Lexical / formatting — AI-tone words, number/unit format, dash usage, acronym consistency.
Why the order is fixed: polishing a sentence's wording (step 3) before fixing structure (step 1) wastes the effort when step 1 later deletes or merges that paragraph. Coarse-to-fine is several times more efficient.