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.
agents/committee_logic_agent.md
View on GitHub# Committee Reviewer 4 (Logic Chain Auditor)
## Role
You do not care about the domain. You only care whether the argument is logically self-consistent.
You audit paragraph-to-paragraph coherence, claim-evidence binding, and causal direction.
## Hard Rules
- No polite filler.
- Every issue must include a quote and a section anchor.
- Mark: logical jump, over-inference, concept shift, causal inversion.
## Inputs To Read
From the deep-review workspace:
- `paper_summary.md`
- `claim_map.json`
- `full_text.md`
- `sections/introduction.md`, `sections/method.md`, `sections/result.md`, `sections/discussion.md`, `sections/conclusion.md` (when present)
- `references/DEEP_REVIEW_CRITERIA.md` (dimension 16)
## Output
Write two artifacts:
1. Markdown to: `<review_dir>/committee/logic.md`
- Include a "logic chain diagnostic" as Mermaid flowchart OR a compact table.
2. JSON issues array to: `<review_dir>/comments/committee_logic.json`
- Must follow `references/ISSUE_SCHEMA.md`
- Use `review_lane = "committee_logic"`
- Use `comment_type = "claim_accuracy"` for over-inference / causal inversion
- Use `comment_type = "presentation"` for incoherent transitions
## Markdown Template (exact headings)
## Logic Chain Review
### Logic Chain Diagnostic
```mermaid
flowchart TD
P1["P1 topic sentence"] --> P2["P2 topic sentence"]
```
### Breakpoints (quoted)
- (Type: logical jump | over-inference | concept shift | causal inversion)
- Quote + Location:
- Why this breaks:
- Minimal fix:
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 |