analysis-revision

Resolve review comments on analysis designs via MCP tools with YAML tracking.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/etoyama/insight-blueprint --skill analysis-revision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analysis-revision
Source: https://github.com/etoyama/insight-blueprint/tree/main/skills/analysis-revision
Command: npx skills add https://github.com/etoyama/insight-blueprint --skill analysis-revision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines the process of addressing reviewer feedback on analysis designs, ensuring every comment is tracked, discussed, and resolved before resubmission.

Core Features & Use Cases

  • Batch selection and validation: Finds the latest revision‑requested review batch and verifies design status.
  • Persistent tracking: Creates and updates a YAML tracking file to resume interrupted sessions and maintain comment fingerprints.
  • Interactive revision loop: Guides the user through each comment with options to fix, skip, or discuss, applying changes via MCP tools.

Quick Start

Run the analysis-revision skill and provide the design ID to begin fixing review comments.

Frequently Asked Questions about analysis-revision

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

FAQPage Schema
How do I track and resolve review comments on analysis designs?

To track review comments on analysis designs, use a revision loop that fetches comments via MCP tools, validates the latest revision batch, and updates a YAML tracking file to record comment fingerprints and resolution status.

What is the best way to resume an interrupted analysis design revision session?

Resuming an interrupted analysis design revision relies on a persistent YAML tracking file that stores batch states and comment fingerprints, allowing the session to pick up exactly where it left off without losing progress.

Do I need MCP tools to automate fixing review feedback on data analysis designs?

Yes, MCP functions are required to retrieve designs, fetch review comments, transition design statuses, and perform file read/write operations to update the YAML tracking file and apply design changes.

How does an interactive revision loop handle skipped or unresolved reviewer feedback?

An interactive revision loop handles reviewer feedback by presenting options to fix, skip, or discuss each comment, ensuring every item is addressed or deliberately deferred before the design status transitions for resubmission.

What are the limitations of using a YAML tracking file for analysis design revisions?

Using a YAML tracking file for analysis design revisions requires continuous MCP file read/write access, meaning revisions cannot be tracked or updated if those specific design retrieval and status transition functions are unavailable.