What problem does it solve?
It solves the problem of porting an already-polished, camera-ready-style paper to a new venue without violating hard constraints like no new experiments, no bibliography edits, and never overwriting prior submissions.
Core Features & Use Cases
- Venue-safe resubmission orchestration: creates a new sibling submission directory and composes the target-venue main file without mutating the original base submission.
- Quality gates before edits: compiles under the target venue style, checks page limits, and runs a multi-layer anonymity scan when applicable.
- Text-only microedits from reviewer feedback: audits proofs/claims/citations, then performs constrained edit-loop iterations using a generated edit whitelist and citation-aware soft-only handling.
- Adversarial residual-risk triage + final export: runs an argument-kill gate to surface unresolved critical issues and then performs final compile + diff reporting, with optional Overleaf push.
Use case: you have a rejected or withdrawn polished paper formatted for venue A, you want to resubmit the same technical work to venue B under a tight deadline, and you must incorporate reviewer concerns only via allowed text microedits.
Quick Start
Run the resubmit-pipeline skill with the polished paper directory, the target venue name, and the review-corpus path to produce a new compiled resubmission folder ready for Overleaf export.
