Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/35-bahayonghang-academic-writing-skills/skills/paper-audit

paper-audit

Verified

Deep-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.

FileKindSize
SKILL.mdskill md14.3 KB
agents/claims_evidence_reviewer_agent.mdmarkdown354 B
agents/committee_editor_agent.mdmarkdown1.9 KB
agents/committee_literature_agent.mdmarkdown1.9 KB
agents/committee_logic_agent.mdmarkdown1.5 KB
agents/committee_methodology_agent.mdmarkdown1.8 KB
agents/committee_theory_agent.mdmarkdown1.9 KB
agents/critical_reviewer_agent.mdmarkdown8.4 KB
agents/domain_reviewer_agent.mdmarkdown7.1 KB
agents/editor_in_chief_agent.mdmarkdown5.2 KB
agents/evaluation_fairness_reviewer_agent.mdmarkdown371 B
agents/literature_reviewer_agent.mdmarkdown3.6 KB
agents/methodology_reviewer_agent.mdmarkdown7.2 KB
agents/notation_consistency_reviewer_agent.mdmarkdown398 B
agents/prior_art_reviewer_agent.mdmarkdown2.9 KB
agents/section_reviewer_agent.mdmarkdown365 B
agents/self_consistency_reviewer_agent.mdmarkdown420 B
agents/synthesis_agent.mdmarkdown951 B
evals/evals.jsonconfig12.0 KB
evals/fixtures/deep_review_fixture.texother699 B
evals/fixtures/gate_ieee_fixture.texother617 B
evals/fixtures/polish_fixture.texother396 B
evals/fixtures/previous_final_issues.jsonconfig1.1 KB
evals/fixtures/previous_review_report.mdmarkdown205 B
evals/fixtures/quick_audit_fixture.texother538 B
examples/gate_example.mdmarkdown3.5 KB
examples/review_example.mdmarkdown2.5 KB
examples/self_check_example.mdmarkdown2.9 KB
references/AUDIT_GUIDE.mdmarkdown3.4 KB
references/CHANGELOG.mdmarkdown530 B
references/CHECKLIST.mdmarkdown6.0 KB
references/CONSOLIDATION_RULES.mdmarkdown907 B
references/DEEP_REVIEW_CRITERIA.mdmarkdown2.8 KB
references/FORBIDDEN_TERMS.mdmarkdown6.4 KB
references/ISSUE_SCHEMA.mdmarkdown928 B
references/LITERATURE_GROUNDING_GUIDE.mdmarkdown3.3 KB
references/POLISH_GUIDE.mdmarkdown2.3 KB
references/QUALITATIVE_STANDARDS.mdmarkdown5.5 KB
references/QUICK_REFERENCE.mdmarkdown1.1 KB
references/REVIEW_CRITERIA.mdmarkdown2.7 KB
references/REVIEW_LANE_GUIDE.mdmarkdown828 B
references/SCHOLAR_EVAL_GUIDE.mdmarkdown6.4 KB
references/SCORING_SYSTEMS.mdmarkdown1000 B
references/SUBAGENT_TEMPLATES.mdmarkdown987 B
references/TROUBLESHOOTING.mdmarkdown1.4 KB
references/VENUE_RULES.mdmarkdown764 B
references/editorial_decision_standards.mdmarkdown6.7 KB
references/quality_rubrics.mdmarkdown10.8 KB
scripts/audit.pyscript78.4 KB
scripts/build_claim_map.pyscript3.3 KB
scripts/check_citations.pyscript5.6 KB
scripts/check_references.pyscript19.9 KB
scripts/consolidate_review_findings.pyscript5.2 KB
scripts/detect_language.pyscript1.9 KB
scripts/diff_review_issues.pyscript2.0 KB
scripts/literature_compare.pyscript11.4 KB
scripts/literature_search.pyscript22.0 KB
scripts/models/scoring_model.jsonconfig737 B
scripts/parsers.pyscript3.3 KB
scripts/pdf_parser.pyscript11.4 KB
scripts/prepare_review_workspace.pyscript6.8 KB
scripts/render_deep_review_report.pyscript3.5 KB
scripts/report_generator.pyscript36.2 KB
scripts/scholar_eval.pyscript13.7 KB
scripts/scoring_model.pyscript6.2 KB
scripts/verify_quotes.pyscript1.6 KB
scripts/visual_check.pyscript10.7 KB
templates/audit_report_template.mdmarkdown2.8 KB
templates/final_issues_template.jsonconfig498 B
templates/review_report_template.mdmarkdown678 B
templates/revision_roadmap_template.mdmarkdown3.1 KB

references/CHECKLIST.md

View on GitHub
# Pre-Submission Checklists

Consolidated checklists for paper audit across venues.

## Universal Checklist (All Venues)

### Compilation & Formatting
- [ ] Paper compiles without errors
- [ ] No overfull/underfull hbox warnings (LaTeX)
- [ ] Page limit respected (excluding references)
- [ ] Correct style file / template used
- [ ] Consistent font sizes and margins

### Content Integrity
- [ ] No placeholder text (TODO, FIXME, XXX)
- [ ] All figures referenced in text
- [ ] All tables referenced in text
- [ ] No orphaned citations (every `\cite` has a bib entry)
- [ ] No unused bibliography entries
- [ ] All equations referenced if numbered
- [ ] Consistent notation throughout

### Writing Quality
- [ ] All acronyms defined on first use
- [ ] No overly long sentences (> 60 words)
- [ ] Abstract is self-contained
- [ ] Abstract contains all 5 structural elements (Background / Objective / Methods / Results / Conclusion)
- [ ] Abstract Results section includes at least one quantitative finding
- [ ] Abstract within venue word count limit
- [ ] Contributions clearly stated in introduction
- [ ] No citation stacking in Introduction/Related Work (max 2 clustered citations per sentence without individual discussion)
- [ ] Limitations section included
- [ ] Figure/Table captions are concise, without AI-like redundancy, and use consistent casing
- [ ] Tables use three-line format (booktabs / no vertical lines)
- [ ] Table captions placed above table, notes placed below
- [ ] Number precision consistent within each table column
- [ ] Statistical significance markers defined in table note when used
- [ ] Literature review uses thematic organization, not author/year enumeration (A1)
- [ ] Each literature theme cluster ends with critical analysis (A2)
- [ ] Related Work concludes with explicit research gap derivation (A3)
- [ ] Discussion contains causal/attribution analysis, not just data repetition (B3)
- [ ] Related Work citations reappear in Discussion for results contextualization (B4)
- [ ] Conclusion contains all three elements: findings summary + implications + limitations/future work (B5)
- [ ] Introduction contribution claims are answered in Conclusion (C3)

### Theory & Conceptual Framework
- [ ] Core theoretical concepts defined clearly and unambiguously (A5)
- [ ] Theoretical framework engages with existing theories, not just cites them (A6)
- [ ] Paper's theoretical contribution is identifiable and stated explicitly (A7)
- [ ] Research gap is genuine and supported by literature evidence, not fabricated by selective citation

### Qualitative Methodology (apply when paper uses qualitative or mixed methods)
- [ ] Sampling strategy described with theoretical/methodological rationale (B6)
- [ ] Data saturation discussed or sample size justified (B7)
- [ ] Coding/analysis process described with sufficient detail: stages, coders, examples (B8)
- [ ] Trustworthiness strategies reported (triangulation, member checking, audit trail, etc.) (B9)
- [ ] Researcher reflexivity addressed for studies involving human participants or sensitive topics (B10)

### Experiment Analysis
- [ ] Experiment section uses cohesive paragraph narratives, not itemized lists
- [ ] Appropriate, up-to-date SOTA baseline methods are included and justified
- [ ] Ablation studies effectively validate the contribution of core components
- [ ] Statistical significance/confidence intervals are reported where applicable

### Submission Compliance
- [ ] Anonymous submission (no author names in blind review)
- [ ] Supplementary material within size limits
- [ ] Code submission prepared (if applicable)
- [ ] Ethics review flagged if applicable

## NeurIPS Specific

- [ ] Paper checklist completed (Appendix)
- [ ] Broader Impact Statement included
- [ ] Lay summary prepared (for accepted papers)
- [ ] Main paper <= 9 pages (+ unlimited references/appendix)
- [ ] Uses official NeurIPS style file
- [ ] Reproducibility details: random seeds, compute, datasets
- [ ] Error bars included with methodology specified
- [ ] Statistical significance tests where appropriate
- [ ] Dataset licensing and consent documented
- [ ] Potential negative societal impacts discussed
- [ ] Comparison with appropriate baselines
- [ ] Ablation studies for key design choices

## ICLR Specific

- [ ] Uses official ICLR style file
- [ ] Double-blind review compliance
- [ ] Main paper <= 10 pages (+ unlimited appendix)
- [ ] Reproducibility statement included
- [ ] Code submission URL provided (if applicable)

## ICML Specific

- [ ] Uses official ICML style file
- [ ] Main paper <= 8 pages (+ unlimited appendix)
- [ ] Impact statement included
- [ ] Supplementary <= 50MB

## IEEE Specific

- [ ] IEEE style file used (conference or journal)
- [ ] Abstract <= 250 words
- [ ] Keywords provided (3-5 terms)
- [ ] References follow IEEE format
- [ ] Figure captions below figures, table captions above tables
- [ ] All figures are high resolution (>= 300 DPI)
- [ ] No floating `algorithm` / `algorithm2e` environment in IEEE pseudocode
- [ ] Pseudocode blocks use a caption and label
- [ ] Pseudocode blocks are referenced in text before appearing
- [ ] Pseudocode line numbers are enabled when helpful for review (recommended, not mandatory)
- [ ] Pseudocode comments are short; paragraph-level explanation stays in the main text

## ACM Specific

- [ ] ACM Computing Classification System (CCS) concepts included
- [ ] ACM Reference Format citation in footer
- [ ] Uses `acmart` document class
- [ ] Rights management information included

## Chinese Thesis Specific (中文学位论文)

- [ ] Bibliography follows GB/T 7714-2015 standard
- [ ] Chinese abstract and English abstract both present
- [ ] Abstract bilingual consistency verified
- [ ] Full-width punctuation used in Chinese text
- [ ] Half-width punctuation used in English text and formulas
- [ ] University template compliance verified
- [ ] Declaration of originality included
- [ ] Acknowledgments section present
- [ ] Keywords in both Chinese and English
- [ ] No author/year enumeration pattern in literature review (A1-ZH: "张三(2019)提出..." consecutive pattern)
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall