agentleFS
ChangChrisLiuChangChrisLiu/academic-writing-audit/skills/reviewer-comment-triage/SKILL.md

reviewer-comment-triage

Skill4 starsChanged 32 days agoMITView on GitHub

Use when translating peer-review comments into prioritized manuscript repairs, checking whether concerns remain in the current source, or separating clarification needs from missing evidence. Useful for revisions and camera-ready checks; does not default to response-letter drafting or new experiments.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use review comments to improve what the paper teaches its reader.

    line 9
  2. Distinctive:

    Stop when every in-scope concern has a supported disposition and the requested repairs are consistent.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reviewer Comment Triage

Use review comments to improve what the paper teaches its reader. A reviewer's question identifies a concern; it does not by itself determine the diagnosis or require a particular experiment.

Read independently

Establish the requested scope and mode: triage, proposed repair, source edit, or verification of a revision. Read the current relevant text and supporting evidence before adopting earlier assistant judgments. A prior PASS may help locate a passage but cannot prove that the present concern is resolved. Retain author-approved choices and well-functioning prose unless the current evidence reveals a concrete defect.

Read each comment for its substantive question. Separate the reviewer's interpretation, the source's actual claim, the evidence available, and the action already taken. If the supplied packet is incomplete, limit the conclusion to it rather than inferring a missing experiment or inventing a revision history.

Establish the right expectation

Choose the disciplinary and methodological lens required by the comment and the paper's study design. Separate the scientific reviewer's question from an editor's clarity or style preference. For each substantive concern, record what a satisfactory argument would establish, why that expectation applies, what the current source establishes, and the remaining difference. Distinguish the actual comment from an inferred reader need. Do not impose a broader scientific claim or another discipline's reporting convention.

For a changed passage, compare the earlier and current versions when supplied. A definition being longer or a reply saying it was clarified does not establish resolution. Check the actual operation and retained claim, while preserving valid motivation, conditions, and interpretation. Accept a supported narrowing or correction, and do not restore incorrect old wording merely for completeness.

Choose a proportionate repair

For each consequential concern, identify its primary cause:

CauseReader-facing action
Correct operation is hard to find or ambiguousState the defining operation where it is needed; keep detailed settings in their appropriate location.
Two parts of the paper disagreeRepair the specific inconsistency using the established source of truth; surface unresolved conflicts.
Claim exceeds the available evidenceNarrow the claim or state the material boundary. Keep the supported finding.
Evidence exists but does not answer the stated questionExplain what it establishes and what remains open.
Concern is already addressed in the current paperRecord the relevant passage and why it answers the concern; do not rewrite merely to demonstrate activity.

Check comparators and ablations by their actual operations, not their names. Removing examples, masking a field, and removing supervision test different things. A temporal split does not establish transfer to another population, and higher performance alone does not identify a mechanism. If a genuinely missing study is essential to the retained claim, mark that dependency explicitly. New experiments are not the automatic consequence of a reviewer asking a broader question; honor the user's chosen scope.

Convert defensive prose into informative content. “We emphasize that our comparison is fair” usually needs a concrete comparison definition, not a stronger assurance. Keep qualifications that change the claim's truth or scope. Remove reviewer-directed staging from the manuscript when its reader-facing substance can stand directly. Draft a response letter only when requested, and do not describe a proposed repair there as completed.

Prose when drafting or revising

When drafting or revising prose, including audit explanations, read prose editing rules. Preserve scientific meaning, necessary reasoning and valid technical terms. Keep sound passages, do not add unreported properties, and limit edits to the requested scope. The local reference covers concept accuracy, clear sentences, repetition and punctuation, including the required exceptions.

Deliver a useful triage

Provide a concise overall judgment and, where several comments are involved, a compact mapping of concern → current evidence/location → decision → smallest repair → unresolved dependency. Prioritize scientific correctness and reader comprehension over stylistic preferences. Include explicit preserve/no-change decisions. Give replacement wording only for the authorized passages, with reasons tied to evidence.

Distinguish proposed wording, changes actually made, source consistency checked, and rendered results inspected. For a repair spanning Methods, captions, tables, or conclusions, verify the connected locations rather than fixing only the quoted sentence. If evidence is unavailable, state exactly what cannot yet be checked.

Stop when every in-scope concern has a supported disposition and the requested repairs are consistent. An unresolved evidence gap can remain honestly documented. Do not expand the task into a full rewrite, unsupported promises, automatic statistical analyses, or a second review of already sound passages.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.