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.
templates/revision_roadmap_template.md
View on GitHub# Revision Roadmap Template
Prioritized action plan generated from audit findings and review assessments.
---
## Template
```markdown
# Revision Roadmap
**Paper**: `{file_path}` | **Date**: {timestamp}
**Based on**: {mode} audit {+ multi-perspective review if applicable}
**Overall Score**: {overall}/6.0 ({score_label})
---
## Priority 1 — Must Address (Blocking)
Issues that must be resolved before submission. Correspond to Critical severity findings.
| # | Task | Source | Section | Est. Effort |
|---|------|--------|---------|-------------|
| R1 | {Specific revision task} | {Module or Reviewer} | {Section X.X} | {hours/days} |
| R2 | {Specific revision task} | {Module or Reviewer} | {Section X.X} | {hours/days} |
### R1: {Task title}
- **Problem**: {What is wrong}
- **Source**: {Which check or reviewer identified this}
- **Requirement**: {What needs to change}
- **Acceptance criteria**: {How to verify it is fixed}
### R2: {Task title}
- **Problem**: {description}
- **Source**: {source}
- **Requirement**: {what to do}
- **Acceptance criteria**: {verification}
---
## Priority 2 — Strongly Recommended
Issues that significantly improve paper quality. Correspond to Major severity findings.
| # | Task | Source | Section | Est. Effort |
|---|------|--------|---------|-------------|
| S1 | {Specific revision task} | {Module or Reviewer} | {Section X.X} | {hours/days} |
| S2 | {Specific revision task} | {Module or Reviewer} | {Section X.X} | {hours/days} |
---
## Priority 3 — Optional Improvements
Style, formatting, and minor issues. Correspond to Minor severity findings.
- [ ] {Minor task — from GRAMMAR, SENTENCES, FORMAT, etc.}
- [ ] {Minor task}
- [ ] {Minor task}
---
## Revision Checklist
### Priority 1 (Must Fix)
- [ ] R1: {task}
- [ ] R2: {task}
### Priority 2 (Should Fix)
- [ ] S1: {task}
- [ ] S2: {task}
### Priority 3 (Nice to Fix)
- [ ] {task}
- [ ] {task}
---
## Estimated Total Effort
| Priority | Items | Est. Time |
|----------|-------|-----------|
| Priority 1 | {count} | ~{X} hours |
| Priority 2 | {count} | ~{Y} hours |
| Priority 3 | {count} | ~{Z} hours |
| **Total** | **{total}** | **~{sum} hours** |
---
## Revision Deadline Guidance
- **Minor Revision scope** (P1 only): 1-2 weeks
- **Major Revision scope** (P1 + P2): 4-6 weeks
- **Full Revision scope** (P1 + P2 + P3): 6-8 weeks
---
## Re-Audit Instructions
After completing revisions, run:
```bash
python audit.py {file_path} --mode re-audit --previous-report {this_report_path}
```
This will verify each item against the revised paper and report:
- FULLY_ADDRESSED / PARTIALLY_ADDRESSED / NOT_ADDRESSED per item
- Any new issues introduced during revision
- Updated scores for comparison
```
---
## Design Principles
1. **Actionability**: Every item is a concrete task, not a vague comment
2. **Traceability**: Every item links back to the source check or reviewer
3. **Prioritization**: P1 > P2 > P3, reflecting impact on paper quality
4. **Time estimation**: Helps authors plan their revision schedule
5. **Verifiability**: Each P1 item has acceptance criteria
6. **Compatibility**: Format works as input for re-audit mode verification
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 |