review2rebuttal

Parse reviewer comments into atomic issues with evidence mapping and rebuttal workspaces.

34|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Henryhe09/Review2Rebuttal --skill review2rebuttal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review2rebuttal
Source: https://github.com/Henryhe09/Review2Rebuttal/tree/main
Command: npx skills add https://github.com/Henryhe09/Review2Rebuttal --skill review2rebuttal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Manually drafting academic paper rebuttals is time-consuming, prone to unsupported claims, and often leads to missed reviewer concerns and disorganized revision tracking. This Skill automates the end-to-end rebuttal workflow to keep responses grounded, traceable, and aligned with paper evidence.

Core Features & Use Cases

  • Atomic Issue Breakdown: Automatically splits raw reviewer comments into structured, trackable issues to ensure no concern is overlooked.
  • Evidence-Grounded Drafting: Maps each issue to paper facts and optional code repository evidence to keep rebuttals accurate and defensible.
  • Dual Workflow Modes: Supports a lightweight quick mode for fast first-round rebuttal drafting, and a rigorous full mode for end-to-end rebuttal work including experiment planning, follow-up handling, and final remarks.
  • Use Case: Researchers responding to peer reviews for academic conferences (e.g., ICLR, ICML, NeurIPS) who need reproducible, auditable rebuttal workspaces instead of disorganized one-off drafts.

Quick Start

Share your paper PDF, reviewer comments, and optional code repository with the AI, and ask it to use the review2rebuttal skill to generate a complete, evidence-backed rebuttal workspace for your paper submission.

Frequently Asked Questions about review2rebuttal

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

FAQPage Schema
How do I write an academic paper rebuttal that directly maps to reviewer comments?

To write an academic paper rebuttal, you can use automated workflows that parse raw reviewer comments into structured atomic issues and map each issue to specific paper facts. This ensures your rebuttal remains grounded, traceable, and aligned with verified paper evidence.

How do I ensure my peer review response only includes claims supported by my code repository?

To ensure your peer review response is supported, evidence mapping links each reviewer issue to facts from your paper and optional code repository. This strict grounding keeps your rebuttal accurate and defensible by bounding claims to verified repository evidence.

Can I draft rebuttals for machine learning conferences like ICLR or NeurIPS quickly?

Yes, you can draft rebuttals for machine learning conferences like ICLR or NeurIPS using a lightweight quick mode. This mode enables fast first-round rebuttal drafting by automatically breaking down reviewer comments into trackable issues for immediate response generation.

What is the best way to plan experiments requested by reviewers during the peer review process?

The best way to plan reviewer-requested experiments is using a rigorous full mode workflow that includes conservative feasibility assessment. This approach evaluates requested experiments for practical viability and integrates them into an auditable, reproducible rebuttal workspace.

Do I need to provide a code repository to generate grounded academic rebuttals?

No, providing a code repository is optional for generating grounded academic rebuttals. The workflow can map evidence strictly to paper facts, but supplying a repository allows deeper evidence grounding and more defensible responses to reviewer concerns.

How do I track and organize multiple reviewer concerns without missing any issues?

To track and organize multiple reviewer concerns without missing issues, automated atomic issue breakdown splits raw comments into structured, trackable items. This creates an auditable on-disk artifact tracking system ensuring every concern is addressed in the final rebuttal.