resubmit-pipeline

Orchestrate a text-only LaTeX resubmission pipeline with compile and anonymity gates.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Shallow-W/llm-wiki --skill resubmit-pipeline-shallow-w
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resubmit-pipeline
Source: https://github.com/Shallow-W/llm-wiki/tree/main/.claude/skills/resubmit-pipeline
Command: npx skills add https://github.com/Shallow-W/llm-wiki --skill resubmit-pipeline-shallow-w

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you resubmit an already polished LaTeX paper to a new venue while strictly preventing new experiments, bibliography edits, or framework changes, and without overwriting prior submissions.

Core Features & Use Cases

  • Constraint-preserving resubmission: creates a new sibling submission directory and freezes the bibliography/framework while allowing only tightly whitelisted text microedits.
  • Reviewer-aware repair loop: ingests prior reviewer reports, runs proof/claim/citation audits, then proposes and applies text-only edits through an automated improvement loop.
  • Safety gates: performs compile validation, page-limit checks, and an anonymity scan (for double-blind targets) plus an adversarial “kill argument” triage gate.
  • Optional Overleaf push: compiles the final paper and can sync the resulting project to Overleaf via the existing Overleaf integration.

Quick Start

Run the resubmit pipeline by pointing it to the polished base paper directory and providing the target venue plus a directory containing prior reviewer reports.

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 LaTeX paper to a different venue without changing the experiments or bibliography?

To resubmit a LaTeX paper safely, use a constraint-preserving workflow that creates a sibling submission directory, freezes the bibliography and framework, and applies only whitelisted text microedits to absorb prior reviewer concerns.

Can I sync my revised LaTeX paper directly to Overleaf after addressing reviewer reports?

Yes, after running text-only microedits, proof and citation audits, and final compilation, you can sync the resulting project directly to Overleaf through the existing Overleaf integration.

How do I incorporate reviewer feedback into my LaTeX manuscript without rewriting the core framework?

Ingest prior reviewer reports to run a reviewer-aware repair loop that proposes text-only edits, applies an automated improvement cycle, and passes a kill-argument risk triage gate while keeping the framework unchanged.

Does the LaTeX resubmission workflow support double-blind venue requirements?

Yes, the resubmission workflow includes an anonymity scan safety gate specifically designed to check for double-blind target venue compliance before final compilation.

What are the limitations of using text-only microedits for paper resubmission?

This microedit approach prohibits new experiments, framework changes, and hard bibliography edits, allowing only soft citation edits to ensure the resubmission does not overwrite or alter the structural baseline of prior submissions.