resubmit-pipeline

Compose a new venue submission from a manuscript and reviewer reports with safety audits.

Updated May 20, 2026
One-click install
npx skills add https://github.com/lightrain-a/medtrace-aris --skill resubmit-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resubmit-pipeline
Source: https://github.com/lightrain-a/medtrace-aris/tree/main/.vendor/aris/skills/resubmit-pipeline
Command: npx skills add https://github.com/lightrain-a/medtrace-aris --skill resubmit-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires latexmk, pdfinfo, rsync, diff, grep, awk, mkdir, tee.

What problem does it solve?

This Skill helps you resubmit an already polished paper to a new venue while honoring hard constraints like no new experiments, no bibliography edits, and never overwriting prior submissions.

Core Features & Use Cases

  • Venue-safe paper composition (text-only microedits): Creates a new sibling submission directory for the target venue and copies the base manuscript content without mutating the original submission.
  • Reviewer-constraint driven improvement: Reads prior reviewer reports, audits proofs/claims/citations, then proposes and applies allowed textual changes via an edit whitelist.
  • Safety gates and triage: Runs compile checks, anonymity scanning (when required), and an adversarial kill-argument gate that flags issues that cannot be fixed under the constraints.
  • Optional Overleaf push: Exports the final compiled submission by delegating to the existing Overleaf sync workflow.

Quick Start

Run resubmit-pipeline on your polished paper directory with a target venue and a folder of the prior reviewer reports to produce a newly composed, compiled resubmission ready for export.

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 LaTeX paper to a new venue without overwriting the original files?

To resubmit a LaTeX paper without overwriting originals, this pipeline creates a sibling submission directory for the target venue and copies the base manuscript content without mutating the prior submission directory.

Can I apply reviewer feedback to my academic writing without adding new experiments or bibliography edits?

Yes, you can apply reviewer feedback via text-only microedits. The pipeline reads prior reviewer reports, audits proofs, claims, and citations, then proposes and applies allowed textual changes through an edit whitelist.

What is the best way to handle page limits and anonymity requirements when migrating an academic paper?

Handling page limits and anonymity requirements during paper migration involves running deterministic safety gates, including compile checks and anonymity scanning, to ensure the finalized output meets the target venue constraints.

Does the resubmission pipeline support Overleaf sync for exporting the final compiled PDF?

Yes, Overleaf sync is supported. The pipeline optionally exports the final compiled submission by delegating to the existing Overleaf sync workflow after passing safety gates and compilation checks.

How to identify unfixable issues in a paper resubmission under hard constraints?

To identify unfixable issues under hard constraints, an adversarial kill-argument gate flags problems that cannot be resolved without violating rules like no new experiments or no bibliography edits.

Do I need latexmk and pdfinfo to run an automated LaTeX resubmission workflow?

Yes, latexmk and pdfinfo are required dependencies. The workflow relies on these tools alongside rsync, diff, and grep to orchestrate compilation checks and file synchronization safely.