Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/16-hsantanna88-clo-author/dot-claude/skills/revise

revise

Verified

R&R cycle — classify referee comments and route to appropriate agents. Replaces /respond-to-referee.

Revise

Structure point-by-point referee responses with classification, agent routing per revision protocol, and diplomatic drafting.

Input: $ARGUMENTS — path to referee report file(s), optionally followed by paper path.


Workflow

Step 1: Parse Inputs

  1. Read referee report(s) from $ARGUMENTS
  2. Read the paper (paper/main.tex or specified path)
  3. Read revision protocol from rules
  4. Read existing scripts to know what analyses already exist

Step 2: Classify Every Comment

ClassRoutingAction
NEW ANALYSIS→ Coder agentFlag for user, create analysis task
CLARIFICATION→ Writer agentDraft rewritten section
REWRITE→ Writer agentDraft structural revision
DISAGREE→ User (mandatory)Draft diplomatic pushback, flag for review
MINOR→ Writer agentDraft fix directly

Step 3: Build Tracking Document

Save to quality_reports/referee_response_tracker.md with:

  • Summary counts per referee
  • Action items by priority (HIGH: new analysis, MEDIUM: clarification, FLAGGED: disagreements, LOW: minor)

Step 4: Dispatch Agents

  • CLARIFICATION/REWRITE → dispatch Writer with specific instructions
  • NEW ANALYSIS → flag for user approval before dispatching Coder
  • DISAGREE → draft diplomatic response, flag prominently for user

Step 5: Draft Response Letter

Generate LaTeX response letter with:

  • Summary of major changes
  • Point-by-point responses with exact referee quotes
  • Color-coded responses
  • Page/section references for each change

Step 6: Diplomatic Disagreement Protocol

When DISAGREE: open with acknowledgment, provide evidence, offer partial concession, NEVER say "the referee is wrong." FLAG for user review.

Step 7: Save Outputs

  1. Tracker: quality_reports/referee_response_tracker.md
  2. Response letter: quality_reports/referee_response_[journal]_[date].tex
  3. Revised sections: paper/sections/ (for CLARIFICATION/REWRITE items)

Principles

  • The response letter is the user's voice. Match their tone.
  • Never fabricate results. Mark NEW ANALYSIS items as TBD.
  • Flag all DISAGREE items. These need human judgment.
  • Track everything. Every comment appears in both tracker and response letter.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall