resubmit-pipeline

Orchestrate a text-only LaTeX resubmission workflow with gated microedits and compile checks.

Updated May 25, 2026
One-click install
npx skills add https://github.com/duypham2801/ThS_LLM --skill resubmit-pipeline-duypham2801
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resubmit-pipeline
Source: https://github.com/duypham2801/ThS_LLM/tree/main/.claude/skills/resubmit-pipeline
Command: npx skills add https://github.com/duypham2801/ThS_LLM --skill resubmit-pipeline-duypham2801

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resubmitting a previously rejected paper to a new venue is risky and slow when constraints forbid new experiments, bibliography edits, framework changes, overwrites, or cross-directory mutations. This Skill orchestrates a gated, text-only microedit workflow that preserves prior submission artifacts while adapting the manuscript to a target venue.

Core Features & Use Cases

  • Venue-safe source composition (no overwrites): Creates a new sibling submission directory for the target venue and copies required LaTeX assets without using cross-directory inputs or symlinks.
  • Compile, page-limit, and anonymity checks (Phase 0.5): Verifies the adapted paper builds, checks page counts against the venue limit, and runs a multi-layer anonymity scan for double-blind constraints.
  • Detect-only audits + controlled microedits (text-only mode): Runs proof, claim, and citation audits (citations in soft-only mode) and then applies whitelisted edits tied to audit findings.
  • Adversarial gate and final verification: Uses a kill-argument residual-risk adjudication, recompiles, re-audits, and produces a diff report; optionally syncs to Overleaf via approved tools.

Quick Start

Run resubmit-pipeline with the polished base paper directory, the target venue name, and a folder containing the prior reviewer reports so the workflow can generate a new submission directory with audit logs and a compile-verified PDF.

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

To resubmit a LaTeX paper without overwrites, you need a text-only resubmission workflow that creates a new sibling submission directory and copies required assets without cross-directory inputs or symlinks, preserving prior submission artifacts.

Can I adapt a LaTeX manuscript for resubmission if the venue forbids new experiments and bibliography edits?

Yes, you can adapt a LaTeX manuscript under strict constraints like no new experiments or bib edits by applying a text-only microedit workflow tied to detect-only proof, claim, and citation audits, ensuring only whitelisted changes are made.

How do I check if a resubmitted LaTeX paper meets double-blind anonymity and page-limit requirements before submission?

Checking anonymity and page limits for a resubmitted LaTeX paper requires a Phase 0.5 compile step that verifies the paper builds, checks page counts against the venue limit, and runs a multi-layer anonymity scan for double-blind constraints.

How do I address prior reviewer concerns when resubmitting a research paper without changing its framework?

Addressing prior reviewer concerns without framework changes involves absorbing prior reviewer reports into a gated workflow that uses a diff-gated improvement loop to apply controlled microedits, ensuring structural changes are strictly prohibited.

What is the best way to sync a compile-verified LaTeX resubmission to Overleaf after applying text-only edits?

The best way to sync a compile-verified LaTeX resubmission to Overleaf is through an optional final workflow phase that produces diff reports and ledger outputs, syncing the adapted paper via approved tools after adversarial gate adjudication.

What happens if a citation audit detects issues in a LaTeX paper during a text-only resubmission?

When a citation audit detects issues during a text-only resubmission, citations are handled in a soft-only mode, allowing the workflow to flag findings and apply whitelisted text-only microedits without modifying the bibliography directly.