review-tracker

Merge review files into a consolidated status document with deduplicated findings.

4|1|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/hisazumi/paper-review-skills --skill review-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-tracker
Source: https://github.com/hisazumi/paper-review-skills/tree/main/skills/review-tracker
Command: npx skills add https://github.com/hisazumi/paper-review-skills --skill review-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates multiple rounds of feedback across reviewers and parts into a single, actionable checklist, eliminating duplicates and enabling tracking of what has been addressed.

Core Features & Use Cases

  • Merge multiple review results into one document to provide a unified view.
  • Deduplicate overlapping issues reported by different reviewers, preserving the most precise wording.
  • Track the status across drafts and reviews (thesis, code, design) and generate a prioritized task list.

Quick Start

Use the review-tracker to merge multiple review files into a single tracking document. For example:

  • /review-tracker feedback1.md feedback2.md --source manuscript.tex --output review_tracking.md

Frequently Asked Questions about review-tracker

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

FAQPage Schema
How do I consolidate feedback from multiple reviewers into a single checklist?

To consolidate feedback from multiple reviewers, ingest multiple review files to identify duplicate findings, assign categories and priorities, and output a single consolidated tracking document.

How do I deduplicate overlapping code review findings across different files?

Deduplicating overlapping code review findings involves ingesting multiple review files, identifying duplicate issues, preserving the most precise wording, and generating a prioritized task list.

Can I track thesis review status across multiple drafts and reviewers?

Yes, you can track thesis review status by merging multiple rounds of feedback into a unified document, eliminating duplicates, and tracking what has been addressed across drafts.

What is the best way to merge multiple review files into a prioritized task list?

The best way to merge review files is to ingest feedback documents, detect and remove duplicate findings, categorize and assign priorities to the remaining issues, and output a consolidated status document.

Does this feedback consolidation approach work for both code reviews and design reviews?

Yes, this feedback consolidation approach works for code reviews, design reviews, and theses where feedback is distributed across files or sections and requires deduplication to reveal priority tasks.

Why do I need to remove duplicates when tracking feedback across multiple reviewers?

Removing duplicates when tracking feedback is necessary because multiple reviewers often report overlapping issues, and deduplication preserves the most precise wording to reveal a clean, prioritized task list.