resubmit-pipeline

Automate academic paper resubmission with text-only edits and Overleaf push.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/xqinag/ARIS-new --skill resubmit-pipeline-xqinag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resubmit-pipeline
Source: https://github.com/xqinag/ARIS-new/tree/main/skills/resubmit-pipeline
Command: npx skills add https://github.com/xqinag/ARIS-new --skill resubmit-pipeline-xqinag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end resubmission workflow for polished academic papers under tight constraints. It orchestrates a text-only rewrite and submission pipeline that prevents new experiments, bib edits, or framework changes, while preserving prior submission provenance by always writing to a new sibling directory.

Core Features & Use Cases

  • Phase-guided workflow: Phase 0 (physical isolation) to Phase 4 (final compile + Overleaf push) with health checks, anonymity scans, audits, microedits, and an adversarial gate.
  • Deterministic, read-only base-dir handling: never overwrites prior submissions; all edits are written to a new sibling venue directory.
  • Use Cases: resubmitting to a different venue under tight deadlines, porting a paper to venue templates, or tightening content without introducing new experiments or bibliography changes.

Quick Start

Provide the polished base paper, target venue, and prior review corpus to initialize a new submission directory and start the Phase 0 workflow.

Frequently Asked Questions about resubmit-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate academic paper resubmission to a new venue without changing my bibliography?

Automate paper resubmission by providing a base manuscript, target venue, and prior review reports to trigger a text-only rewrite pipeline that enforces no bibliography edits and writes to a new sibling directory.

What is a text-only paper rewrite workflow for resubmission?

A text-only rewrite workflow restricts revisions to manuscript prose, enforcing no new experiments, framework changes, or bibliography edits, while preserving prior submission provenance in a new directory.

How do I port a paper to a new venue template while keeping prior submissions intact?

Port a paper by initializing a new sibling venue directory from your base manuscript, ensuring deterministic read-only handling of prior submissions and pushing the final compiled package to Overleaf.

Can I add new experiments when resubmitting a paper through this workflow?

No, you cannot add new experiments; the resubmission workflow enforces strict constraints including no new experiments, no bibliography edits, and immutable prior submissions to ensure a compliant text-only revision.

What inputs do I need to start the paper resubmission workflow?

You need to provide exact inputs: a polished base manuscript, the target venue, and prior review reports to initialize the submission directory and begin the Phase 0 isolation workflow.

Does the resubmission workflow support pushing the final compiled paper to Overleaf?

Yes, the workflow supports Overleaf integration; Phase 4 executes the final compile and pushes the compliant submission package directly to Overleaf after passing health checks and an adversarial gate.