resubmit-pipeline

Orchestrate text-only paper resubmissions to new venues with prior reviewer reports.

2|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/raja21068/AutoResearch --skill resubmit-pipeline-raja21068
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resubmit-pipeline
Source: https://github.com/raja21068/AutoResearch/tree/main/skills/aris/resubmit-pipeline
Command: npx skills add https://github.com/raja21068/AutoResearch --skill resubmit-pipeline-raja21068

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of quickly porting an already-polished, execution-verified paper to a different venue while respecting strict resubmission constraints like no new experiments, no bibliography edits, and no overwriting of prior submissions.

Core Features & Use Cases

  • Text-only microedit resubmission orchestration: creates a fresh target-venue sibling directory, compiles, audits, and applies constrained edits to address reviewer concerns without modifying bib files or venue templates.
  • Execution-grounded quality gates: runs proof/audit/claim/citation checks and composes an evidence-backed improvement loop, including a citation audit in soft-only mode to avoid bib mutations.
  • Risk control for high-stakes resubmits: performs an anonymity scan and a kill-argument adversarial gate to flag unresolved critical issues that require user escalation.
  • Finalization & export support: compiles, produces a full diff report, and optionally pushes the result to Overleaf via the existing overleaf-sync workflow.

Quick Start

Run resubmit-pipeline with the paper-base directory, target venue, and the folder of prior reviewer reports to generate a new venue submission folder with microedits and a compile-verified result.

Frequently Asked Questions about resubmit-pipeline

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

FAQPage Schema
How do I resubmit a rejected academic paper to a new venue without changing the bibliography?

To resubmit a rejected academic paper without changing the bibliography, you can use a text-only resubmission workflow that applies constrained microedits to address reviewer concerns while enforcing a soft-only citation audit to avoid any bibliography mutations.

What is a text-only microedit workflow for LaTeX paper resubmission?

A text-only microedit workflow for LaTeX paper resubmission is a process that creates a fresh target-venue sibling directory, compiles the document, and applies constrained edits to address prior reviewer reports without overwriting previous submission directories or adding new experiments.

Can I push a resubmitted LaTeX paper directly to Overleaf after making microedits?

Yes, you can push a resubmitted LaTeX paper directly to Overleaf after finalizing microedits, compile verification, and page-limit checks by utilizing the optional Overleaf push functionality within the resubmission workflow.

How do I perform an anonymity check on a LaTeX manuscript before resubmitting?

To perform an anonymity check on a LaTeX manuscript before resubmitting, the resubmission pipeline runs an automated anonymity scan designed to flag potential identity disclosures and unresolved critical issues requiring user escalation.

What is the best way to address reviewer reports when porting a paper to a new academic venue?

The best way to address reviewer reports when porting a paper is to run an adversarial kill-argument triage and an evidence-backed improvement loop, applying only whitelisted microedits to resolve claims without altering original experimental data.

What are the limitations of a text-only resubmission pipeline for academic papers?

Limitations of a text-only resubmission pipeline include the strict inability to add new experiments, modify bibliography files, or alter venue templates, meaning unresolved critical issues flagged by the adversarial gate require manual user escalation.