brycewang-stanford/Auto-Empirical-Research-Skills / skills/35-bahayonghang-academic-writing-skills/skills/paper-audit
paper-audit
VerifiedDeep-review-first audit for Chinese and English academic papers across LaTeX, Typst, and PDF formats. Use whenever the user wants reviewer-style paper critique, pre-submission readiness checks, pass/fail gate decisions, structured revision roadmaps, or re-audits of revised manuscripts. Trigger even if the user only says "review my paper", "check if this is ready to submit", "audit this PDF", "simulate peer review", "find the biggest problems in this manuscript", or "re-check whether I fixed the review issues". Do not use for direct source editing or compilation-heavy repair; route those to the format-specific writing skills instead.
references/AUDIT_GUIDE.md
View on GitHub# Audit Guide
How to use the paper-audit skill and interpret its results.
## Quick Start
```bash
# Basic quick audit
python scripts/audit.py paper.tex --mode quick-audit
# Deep review
python scripts/audit.py paper.tex --mode deep-review
# Quality gate (pass/fail)
python scripts/audit.py paper.pdf --mode gate --pdf-mode enhanced
# Chinese thesis
python scripts/audit.py thesis.tex --lang zh --venue thesis-zh
```
## Mode Selection Guide
| Scenario | Recommended Mode | Why |
|----------|-----------------|-----|
| "Is my paper ready to submit?" | `quick-audit` | Fast readiness analysis |
| "What would reviewers say?" | `deep-review` | Reviewer-style issue bundle and roadmap |
| "Can my student submit this?" | `gate` | Fast pass/fail check |
| "Quick sanity check before deadline" | `gate` | Fastest, checks essentials only |
| "I want detailed feedback" | `deep-review` | Most comprehensive output |
## Understanding the Report
### Quick-Audit Report
The quick-audit report contains:
1. **Executive Summary**: Overall score and issue count at a glance
2. **Scores Table**: Per-dimension scores with issue counts (Critical/Major/Minor)
3. **Issues List**: All findings sorted by severity
4. **Pre-Submission Checklist**: Pass/fail for each checklist item
**How to read scores**:
- **5.0+**: Excellent — minor polish only
- **4.0-5.0**: Good — address Major issues
- **3.0-4.0**: Needs work — significant revisions required
- **< 3.0**: Major concerns — consider restructuring
### Deep Review Report
The deep review report adds:
- **Overall Assessment**: short calibrated reviewer summary
- **Major / Moderate / Minor Issues**: quote-anchored structured findings
- **Revision Roadmap**: prioritized fix list
- **Recommendation**: score summary, if requested
### Gate Report
Binary verdict:
- **PASS**: All mandatory checks passed, no critical issues
- **FAIL**: Blocking issues found — must fix before submission
## PDF Input Considerations
PDF mode has inherent limitations:
| Feature | LaTeX/Typst | PDF Basic | PDF Enhanced |
|---------|-------------|-----------|-------------|
| Section detection | Exact | Heuristic | Good |
| Math verification | Full | Unavailable | Unavailable |
| Format checking | Full | Skipped | Skipped |
| Figure references | Full | Skipped | Skipped |
| Grammar analysis | Full | Good | Good |
| Logic analysis | Full | Good | Good |
| Bibliography | Full | Skipped | Skipped |
**Recommendation**: Use source files (.tex/.typ) whenever possible for maximum accuracy. Use PDF mode for quick reviews when source is unavailable.
## Addressing Issues
### Priority Order
1. **Critical (P0)**: Must fix — these will likely cause rejection
2. **Major (P1)**: Should fix — these weaken the paper significantly
3. **Minor (P2)**: Nice to fix — these improve polish
### Common Critical Issues
- Missing figure/table references
- Compilation errors
- Placeholder text (TODO/FIXME)
- Author names in blind submission
### Common Major Issues
- Long, convoluted sentences
- Logic gaps in methodology
- Missing baselines or ablations
- AI-trace patterns in writing
### Common Minor Issues
- Minor grammar issues
- Inconsistent notation
- Style guide violations
## Re-auditing After Fixes
After addressing issues, re-run the audit to verify improvements:
```bash
# Before fixes
python scripts/audit.py paper.tex -o report_before.md
# After fixes
python scripts/audit.py paper.tex -o report_after.md
```
Compare scores to track improvement.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |