Claude Prompt Library

30 Claude Prompts for Peer Review Comments You Can Sign

30 copy-paste prompts

XML prompts for a first read, major and minor comments, methods critique, a decision letter, and an author-response map. Paste the manuscript. Claude invents no citations or findings. You edit the report, then submit the review.

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

Louis Corneloup
By Louis Corneloup · Founder, Techpresso
Last updated ·Hand-curated & tested by the AI Academy team

First Read

5 prompts

Summarize the Manuscript as Submitted

1/30

✨ What it does

Claude writes a first-read summary of [PASTE MANUSCRIPT] that restates the aims, methods, results, and limits as the authors wrote them. You edit the comments, then submit the review.

<context> I am doing a first read of a manuscript I will review. Restate what the authors actually wrote. Do not invent citations, findings, counts, or a literature I have not pasted. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Venue: [VENUE] - Review type: [JOURNAL / CONFERENCE / COURSE / GRANT] - My role: [REVIEWER / ASSOCIATE EDITOR / STUDENT REVIEWER] </inputs> <task> Write a first-read summary from [PASTE MANUSCRIPT] only: (1) the question or aim in one sentence, (2) the design or approach as stated, (3) the results or claims as stated, (4) the limits the authors already named, (5) what the paper does not claim. If a heading is empty in the paste, write NOT IN PASTE. </task> <constraints> - Do not invent papers, authors, years, DOIs, quotations, findings, n, or p-values. - Do not upgrade a hedge into a proof. - Do not import a classic paper as background. - If a claim needs a source or number I did not paste, mark it UNVERIFIED. - This is a map of the submission, not yet a verdict. </constraints> <format> Numbered summary, then a NOT IN PASTE list, then an UNVERIFIED list. </format>

💡

Pro tip: Paste the full manuscript, not the abstract alone. A first read from the abstract will praise a paper the body never delivered.

Map Claims to Pasted Evidence

2/30

✨ What it does

Claude maps each claim in [PASTE MANUSCRIPT] to evidence that appears in the paste and tags stretch or not in paste. You edit the comments, then submit the review.

<context> I need an honesty map: does [PASTE MANUSCRIPT] say only what its own text and tables support? Do not repair a weak claim with a paper I did not paste. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Claims I already distrust: [WATCH LIST OR NONE] - Venue: [VENUE] </inputs> <task> For each material claim in the abstract, results, and discussion: tag MATCH (the paste supports it), STRETCH (stronger than the paste), or NOT IN PASTE. Quote a short supporting phrase for MATCH. Do not invent the missing evidence. Propose a weaker wording the authors could keep. </task> <constraints> - Do not invent findings, counts, or citations. - Do not treat your memory of a famous paper as evidence. - If the draft cites a work with no bibliographic line in the paste, flag CITE NOT IN PASTE. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Claim table: location, quote, tag, quoted support or none, weaker wording. Then CITE NOT IN PASTE and UNVERIFIED lists. </format>

💡

Pro tip: Run this before you write major comments. STRETCH tags are the sentences that fail if the authors push back.

Flag Scope and Contribution

3/30

✨ What it does

Claude flags whether the contribution claim in [PASTE MANUSCRIPT] matches the scope and findings that actually appear in the paste. You edit the comments, then submit the review.

<context> I need to see whether the contribution claim matches the work on the page. Do not invent a result that would make a loud contribution look earned. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Contribution sentence I spotted, if any: [CONTRIBUTION LINE OR FIND IT] - Venue: [VENUE] - Field: [FIELD] </inputs> <task> Extract the contribution claim (or the nearest thing to one). Map it against scope, design, and findings in the paste. Tag the claim SUPPORTED, STRETCH, or NOT IN PASTE. Write a smaller contribution the paste can carry, or say DROP. Do not add a paper that would save the loud claim. </task> <constraints> - Do not invent papers, data, or a finding the study did not report. - Do not treat expected outcomes as completed results. - Prefer "this manuscript shows X in this set" over "the field has never." - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Contribution quote, tag, smaller claim or DROP, scope mismatch list, UNVERIFIED rows. </format>

💡

Pro tip: Read the last paragraph of the introduction next to the results. A contribution that names a theory the results never test is a major comment, not a compliment.

List What Is Missing From the Paste

4/30

✨ What it does

Claude lists missing methods, counts, or citations that [PASTE MANUSCRIPT] still needs for a fair review, without inventing them. You edit the comments, then submit the review.

<context> I cannot finish a fair review until I know what the authors omitted. List gaps. Do not fill them with invented n, instruments, or papers. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Venue checklist if I have one: [VENUE RULES OR NONE] - Sections I expect in this field: [EXPECTED SECTIONS] </inputs> <task> List what is missing from the paste for a complete review: methods cells, counts, ethics status, figure-to-text links, and citations that are named in text but have no record. For each gap: why a reviewer needs it, and a one-line request I can paste into the report. Do not supply the missing fact. </task> <constraints> - Do not invent the missing n, DOI, approval number, or paper. - Do not invent a journal rule I did not paste. - If [VENUE RULES OR NONE] is NONE, keep rules as blank checks, not guessed house style. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Numbered gaps with a request line each, then a MUST-ASK-AUTHORS list, then UNVERIFIED rows. </format>

💡

Pro tip: Ask for the missing cell, not a better paper. A review that invents the n the authors forgot is no longer a review.

Write a Neutral First-Impression Memo

5/30

✨ What it does

Claude writes a neutral first-impression memo on [PASTE MANUSCRIPT] for [VENUE] that separates praise from problems you can show. You edit the comments, then submit the review.

<context> I need a calm first-impression memo before I write numbered comments. Separate what I can praise from what I can challenge. Do not invent a finding or a comparison paper. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Venue: [VENUE] - Field: [FIELD] - Tone I must keep: [FIRM / CIVIL / BLUNT] - Known conflict or limit of mine: [MY LIMIT OR NONE] </inputs> <task> Write a first-impression memo: (1) one-sentence gist, (2) two strengths I can quote from the paste, (3) two problems I can quote from the paste, (4) what I still need from the authors, (5) a provisional decision family only (accept-minor / R&R / reject) with a one-line reason. No invented praise. </task> <constraints> - Do not invent papers, findings, or a reviewer identity. - Do not write the full comment list in this memo. - If a strength is only a vibe, drop it. - Include [MY LIMIT OR NONE] as a recusal note if I named one. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Memo with five headed sections, then UNVERIFIED rows. No decision letter yet. </format>

💡

Pro tip: Keep praise tied to a pasted sentence. Empty this is an important paper is how you talk yourself into a softer decision than the methods deserve.

Major Comments

5 prompts

Critique the Question Fit

6/30

✨ What it does

Claude critiques whether [PASTE MANUSCRIPT] answers [RESEARCH QUESTION OR AIM] using only claims and results that appear in the paste. You edit the comments, then submit the review.

<context> I need a major comment on whether this manuscript answers the question it set. Argue from the paste only. Do not invent a better question from a paper I did not paste. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Question or aim as I read it: [RESEARCH QUESTION OR AIM] - Venue: [VENUE] - Field: [FIELD] </inputs> <task> Write one major comment on question fit: quote the aim, quote what the results actually speak to, name the mismatch if any, and say what would close it without inventing new data. If the paste answers the aim, say so and do not invent a problem. </task> <constraints> - Do not invent papers, findings, or a different research question the authors "should have" asked unless the paste already states that aim. - Do not demand a design they did not run. - If the paste is too thin to judge fit, write NEED NOTES, not a guess. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> One numbered major comment (quote / mismatch / request), then UNVERIFIED rows. </format>

💡

Pro tip: Quote the aim and the last results sentence side by side. If they name different objects, that is a major comment, not a copy-edit.

Challenge the Gap Claim

7/30

✨ What it does

Claude challenges the gap claim in [PASTE MANUSCRIPT] using only papers named in the paste, and will not invent a missing classic. You edit the comments, then submit the review.

<context> Reviewers reject papers when the gap is louder than the cited set. Stress-test the gap from papers the authors named. Do not invent a missing classic. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Gap sentence I spotted, if any: [GAP STATEMENT OR FIND IT] - Reference list if separate: [PASTE REFERENCE LIST OR IN MANUSCRIPT] </inputs> <task> Audit the gap claim against the cited set in the paste. Tag STRONG / STRETCH / NOT IN PASTE. If it is louder than the notes, rewrite a weaker gap the authors can defend. List searches they still owe as types, not as invented titles. </task> <constraints> - Do not invent papers, authors, years, DOIs, or quotations. - Do not claim "nobody has studied X" unless the paste supports "not in this cited set." - Do not fill a hole with a recalled famous paper. Write SEARCH FOR that topic instead. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Verdict, quoted gap, weaker rewrite the authors could use, search-to-run list, UNVERIFIED rows. </format>

💡

Pro tip: Write the gap as not in this manuscript's cited set, not the field has never. Reviewers who invent the missing classic get a rebuttal they cannot answer.

Test Results Against Claims

8/30

✨ What it does

Claude tests whether results in [PASTE MANUSCRIPT] support the discussion claims and tags any finding that is not in the paste. You edit the comments, then submit the review.

<context> I need major comments on overclaimed results. The discussion may say more than the tables. Do not invent the number that would make a stretch true. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Results tables or excerpts: [PASTE RESULTS OR IN MANUSCRIPT] - Discussion claims I distrust: [WATCH LIST OR NONE] </inputs> <task> Pair each material discussion claim with the result line that is supposed to carry it. Tag MATCH, STRETCH, or NOT IN PASTE. Write a major comment only where the paste shows a stretch. Offer a weaker sentence the authors can keep. No new findings. </task> <constraints> - Do not invent n, p-values, effect sizes, or a table cell. - Do not invent a comparison study. - If a count is missing, write NOT IN PASTE, not a rounded guess. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Table: discussion quote | result quote or none | tag | major-comment draft or NONE. Then UNVERIFIED rows. </format>

💡

Pro tip: Start in the discussion, then walk backward to the table. Claims that only exist in the discussion are the ones you must not invent a p-value for.

Name a Fatal Design Problem

9/30

✨ What it does

Claude names a fatal or near-fatal design problem in [PASTE MANUSCRIPT] only if the paste shows it, and will not invent a better headcount. You edit the comments, then submit the review.

<context> I need to know whether this design can support the claims, or whether the problem is fatal. Do not invent a larger n or a second coder that would save it. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Design as I read it: [STUDY DESIGN] - Venue bar: [VENUE] - What I will not demand: [OFF LIMITS] </inputs> <task> Decide if a design problem in the paste is FATAL, FIXABLE, or NOT SHOWN. Quote the methods line. Explain what the design can and cannot support. If FATAL, write the comment a decision letter can reuse. If NOT SHOWN, ask for the missing cell instead of guessing. </task> <constraints> - Do not invent n, an instrument, a second rater, or a finding. - Do not invent a methods citation that would bless or kill the design. - Honor [OFF LIMITS]. Do not demand a trial they did not run unless the claims require it and the paste shows the mismatch. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Verdict, quoted line, can-support / cannot-support, comment draft or NEED CELL, UNVERIFIED rows. </format>

💡

Pro tip: A fatal comment needs a quote from their methods. If you cannot point at the line, it is a preference, not a reject reason.

Rank Major Comments by Severity

10/30

✨ What it does

Claude ranks major comments on [PASTE MANUSCRIPT] by severity for [VENUE] and drops any comment that needs a paper you did not paste. You edit the comments, then submit the review.

<context> I have a first read and some notes. I need a ranked major-comment list I can sign. Drop any comment that needs a paper, finding, or rule I did not paste. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - My notes: [PASTE NOTES] - Venue: [VENUE] - How many majors I will keep: [3 TO 6] </inputs> <task> Write [3 TO 6] major comments, ranked by severity for [VENUE]. Each comment: a short heading, a quote from the paste, why it matters, and a concrete request. Merge duplicates. Move copy-edits to a MINOR parking list. Delete any comment that needs an invented source. </task> <constraints> - Do not invent papers, findings, or journal rules. - Do not write more majors than I asked for. - If two notes are the same problem, merge them. - If a comment cannot be tied to a quote, drop it or mark NEED QUOTE. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Ranked major comments, then a MINOR parking list, then dropped-as-unfounded rows, then UNVERIFIED rows. </format>

💡

Pro tip: Keep three to six majors. A list of fifteen majors is a minor-comment dump with louder headings.

Minor Comments

5 prompts

Write Line-Level Clarity Notes

11/30

✨ What it does

Claude writes line-level clarity comments on [PASTE MANUSCRIPT] that fix wording, not the argument, and add no new citations. You edit the comments, then submit the review.

<context> I need minor comments on clarity. Fix wording and structure the authors already wrote. Do not add a new argument or a new citation. </context> <inputs> - Manuscript or marked pages: [PASTE MANUSCRIPT] - Pages or sections to stay in: [SECTION SCOPE] - Venue style notes if any: [VENUE RULES OR NONE] </inputs> <task> Write line-level minor comments: quote the line, name the problem (ambiguity, overloaded sentence, undefined term, missing cross-reference), and offer a rewrite that does not change the claim. Skip argument fights. Those belong in majors. </task> <constraints> - Do not invent citations, findings, or a better theory name. - Do not turn a minor into a major by demanding new data. - Do not invent a journal style rule I did not paste. - If a rewrite would change the claim, stop and tag MOVE TO MAJORS. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Numbered minors: location, quote, problem, rewrite. Then MOVE TO MAJORS, then UNVERIFIED rows. </format>

💡

Pro tip: Point at a sentence, not a vibe. Unclear in places is not a comment the authors can fix.

Check Figures Against the Text

12/30

✨ What it does

Claude checks figures and tables in [PASTE MANUSCRIPT] against the results text and flags mismatches that appear in the paste. You edit the comments, then submit the review.

<context> I need minor (or major, if the mismatch is fatal) comments on figures and tables versus the results prose. Use only what I pasted. Do not invent a cell. </context> <inputs> - Manuscript, including figure and table text: [PASTE MANUSCRIPT] - Extra captions or notes: [PASTE CAPTIONS OR NONE] - Venue: [VENUE] </inputs> <task> Check each figure and table mentioned in the paste against the results sentences that cite it. Flag: missing call-out, caption that claims more than the table, number that does not match the prose, and axes or units that the text never defines. Do not invent the missing number. </task> <constraints> - Do not invent n, a data point, or a figure that is not in the paste. - If a figure is named but not shown, write FIGURE NOT IN PASTE and ask for it. - Do not add a citation to "standardize" a caption. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Table: item | text quote | figure or table quote or NONE | mismatch | comment draft. Then UNVERIFIED rows. </format>

💡

Pro tip: If a figure is missing from the paste, ask for it. Do not describe the figure you assume they meant.

Check Cites Against the Paste

13/30

✨ What it does

Claude checks in-text cites in [PASTE MANUSCRIPT] against [PASTE REFERENCE LIST] and will not add a work that is not in the paste. You edit the comments, then submit the review.

<context> I pasted the manuscript and the reference list the authors used. Check completeness. Do not complete records from memory and do not add readings. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Reference list: [PASTE REFERENCE LIST] - Citation style: [CITATION STYLE] </inputs> <task> Cross-check in-text cites against [PASTE REFERENCE LIST]: cites with no reference, references with no cite, duplicate entries, and missing fields. Mark suspect (tidy but implausible) entries as SUSPECT, VERIFY OR DELETE. Output only their items. </task> <constraints> - Do not add a reference they did not paste. - Do not fill a missing DOI, page range, or author from memory. - Do not invent the missing in-text match. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Mismatch lists, missing-field list, suspects, then minor-comment drafts I can paste. UNVERIFIED rows last. </format>

💡

Pro tip: Unused references are not a crime. Forcing Claude to invent the missing match is.

Flag Terminology Drift

14/30

✨ What it does

Claude flags terminology drift in [PASTE MANUSCRIPT] for [TERM LIST] so each key term keeps one meaning the authors already used. You edit the comments, then submit the review.

<context> I need minor comments when key terms change meaning mid-paper. Use only definitions the draft already supports. Do not cite a theorist I did not paste. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Terms to lock: [TERM LIST] - Definitions the authors already gave, if any: [DEFINITIONS OR NONE] </inputs> <task> Find every use of each term in [TERM LIST] and of close variants. Propose one locked definition per term from wording already in the paste (or from [DEFINITIONS OR NONE]). List drifted sentences as minor comments. If one word is used two ways, show both and ask the authors to pick. </task> <constraints> - Do not import a textbook definition from memory if they did not paste one. - Do not add sources. - Do not treat a methods synonym as drift if the paste defines both as the same measure. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Term, locked definition, variant list, numbered minor comments, UNVERIFIED rows. </format>

💡

Pro tip: Lock three terms, not twenty. If construct, measure, and outcome drift, the results section is already a major comment.

Copy-Edit Without New Claims

15/30

✨ What it does

Claude copy-edits [PASTE MANUSCRIPT] for grammar and venue style in [CITATION STYLE] without adding claims or citations. You edit the comments, then submit the review.

<context> I need a copy-edit pass that does not change the science. No new claims, no new citations, no invented house rule. </context> <inputs> - Manuscript or excerpt: [PASTE MANUSCRIPT] - Citation style: [CITATION STYLE] - Venue rules if I have them: [VENUE RULES OR NONE] - Words the journal bans, if any: [BANNED WORDS OR NONE] </inputs> <task> Write minor copy-edit comments: grammar, agreement, figure call-outs, [CITATION STYLE] consistency on records that already exist, and any rule in [VENUE RULES OR NONE]. Keep every citation unchanged except for style on fields they already supplied. </task> <constraints> - Do not add sources or findings. - Do not invent a journal rule I did not paste. - Do not replace a hedge with a stronger verb for elegance. - If [VENUE RULES OR NONE] is NONE, skip house-style guesses. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Numbered copy-edits with location and a short fix. Then a do-not-touch list (claims you left alone). UNVERIFIED rows last. </format>

💡

Pro tip: Keep this pass last. If you copy-edit first, you will keep a broken argument because the sentences sound finished.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.

Try AI Academy Free

Methods Critique

5 prompts

Audit Sample or Corpus

16/30

✨ What it does

Claude audits the sample or corpus in [PASTE MANUSCRIPT] and leaves the headcount unknown unless the authors stated it in the paste. You edit the comments, then submit the review.

<context> I will paste the methods I have. Describe and critique only that sample or corpus. Do not complete a missing n from a typical paper in this field. </context> <inputs> - Manuscript or methods: [PASTE MANUSCRIPT] - Design as I read it: [STUDY DESIGN] - Headcount if I can see it: [SAMPLE N OR UNKNOWN] - Venue: [VENUE] </inputs> <task> Audit the sample or corpus: who or what is in the set, how they enter, who is missing, and the n they supplied. If [SAMPLE N OR UNKNOWN] is UNKNOWN, keep every sentence n-free and list the cells the authors must add. Write comments a reviewer can sign. </task> <constraints> - Do not invent n, a response rate, a demographic split, or an archive they did not name. - If a cell is missing, write NOT IN PASTE. - Do not upgrade a convenience sample into a representative one. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Audit prose, table of known vs NOT IN PASTE fields, numbered comments, UNVERIFIED rows. </format>

💡

Pro tip: If n is missing, ask for it. Completing a typical sample size from your field is a misconduct risk.

Stress-Test Analysis Choices

17/30

✨ What it does

Claude stress-tests analysis choices in [PASTE METHODS] against [RESEARCH QUESTION] and will not invent a test the authors did not run. You edit the comments, then submit the review.

<context> I need a methods critique of the analysis they described, not a new analysis I wish they had run. Do not invent a test, a model, or an n they did not name. </context> <inputs> - Methods or analysis section: [PASTE METHODS] - Research question or aim: [RESEARCH QUESTION] - Software they named, if any: [SOFTWARE OR NONE] - Sample n if known: [SAMPLE N OR UNKNOWN] </inputs> <task> Stress-test the analysis against [RESEARCH QUESTION]: units, preparation, primary analysis, secondary or exploratory work, missingness if they mentioned it, and what the analysis cannot support. Write comments that ask for clarification or a weaker claim, not a new dataset. </task> <constraints> - Do not invent n, p-values, effect sizes, or a finding they did not report. - Do not add a test they cannot have run unless you label it OPTIONAL, THEY DID NOT RUN THIS. - If [SAMPLE N OR UNKNOWN] is UNKNOWN, refuse a power claim. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Numbered analysis comments, will-not-support list, OPTIONAL tests clearly marked as not in the paste, UNVERIFIED rows. </format>

💡

Pro tip: Name the analysis they ran, then say what it cannot support. Demanding a model they never claimed is how reviews turn into wish lists.

Check Ethics Wording

18/30

✨ What it does

Claude checks ethics and consent wording in [PASTE MANUSCRIPT] against [ETHICS STATUS] and invents no approval number. You edit the comments, then submit the review.

<context> I need ethics comments that match what the authors stated. Do not invent an approval number, a waived review, or a population they cannot have reached. </context> <inputs> - Manuscript or ethics paragraph: [PASTE MANUSCRIPT] - Ethics status as I can see it: [ETHICS STATUS] - Data type: [HUMAN / ARCHIVAL / PUBLIC / OTHER] - Known risks I spotted: [KNOWN RISKS OR NONE] </inputs> <task> Check ethics and consent wording: approval status only as they stated it, consent or data-use notes from the paste, risks they named, and limits they already accept. Write comments that ask for a missing statement. Separate ethics facts from study limits. </task> <constraints> - Do not invent an IRB, REB, or ethics ID. - If [ETHICS STATUS] is NONE or silent, write that the review must not claim they have approval. - Do not invent a risk-closing procedure they did not name. - Include a note if they used an AI tool and the venue asked for disclosure, but only if I pasted that rule. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Ethics comments, consent comments, missing-statement list, UNVERIFIED rows. </format>

💡

Pro tip: If the approval number is blank, ask the authors. Claude completing an ethics ID from memory is a misconduct risk for you too.

Flag Overclaimed Causal Language

19/30

✨ What it does

Claude flags causal language in [PASTE MANUSCRIPT] that overreaches [STUDY DESIGN] and rewrites a weaker line the paste can carry. You edit the comments, then submit the review.

<context> I need a hostile language audit: does the manuscript claim more cause than the design can support? Do not repair an overclaim with extra data they did not collect. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Design: [STUDY DESIGN] - Data they had: [DATA ACCESS OR IN MANUSCRIPT] - Sample n if known: [SAMPLE N OR UNKNOWN] </inputs> <task> Audit [PASTE MANUSCRIPT] for causal overclaim: prove, show, effect of, representative, dual coding they did not name, or a completed result written stronger than the table. For each: quote the line, name the overclaim, and rewrite a weaker line they can keep. </task> <constraints> - Do not invent n, a second coder, an instrument, or a finding. - Do not invent a methods citation to bless the design. - If [SAMPLE N OR UNKNOWN] is UNKNOWN, refuse a power or representativeness claim. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Table: quoted line | overclaim | weaker rewrite | major or minor. Then UNVERIFIED rows. </format>

💡

Pro tip: Search the draft for show, prove, and effect of. Those three are where causal overclaim usually sits.

Write a Methods-Only Review Block

20/30

✨ What it does

Claude writes a methods-only review block on [PASTE METHODS] for [VENUE] that stays inside the protocol the authors pasted. You edit the comments, then submit the review.

<context> I need the methods section of my reviewer report, not the whole letter. Stay inside the protocol they pasted. Do not invent a second protocol. </context> <inputs> - Methods text: [PASTE METHODS] - Venue: [VENUE] - Design as I read it: [STUDY DESIGN] - Question or aim: [RESEARCH QUESTION] - My methods notes: [PASTE NOTES OR NONE] </inputs> <task> Write a methods-only review block: design fit, sample or corpus, collection, analysis, validity or trustworthiness, ethics as stated, and limits. Use future or past tense only as the authors did. Leave counts as UNKNOWN unless they pasted them. Number comments as major or minor. </task> <constraints> - Do not invent n, instruments, software, or a second reviewer. - If they worked alone, do not upgrade that to dual independent coding. - Do not write literature or contribution comments in this block. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Methods review block with numbered comments tagged MAJOR or MINOR, UNKNOWN cells, UNVERIFIED rows. </format>

💡

Pro tip: If you will also review the literature, keep this block methods-only. Mixed blocks are how a methods fight hides a missing citation you invented.

Decision Letter

5 prompts

Draft a Revise-and-Resubmit Letter

21/30

✨ What it does

Claude drafts a revise-and-resubmit letter on [PASTE MANUSCRIPT] for [VENUE] that lists only comments you can defend from the paste. You edit the letter, then submit the review.

<context> I have decided this manuscript can come back. Draft a revise-and-resubmit letter I can edit. Use only comments I can defend from the paste. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Venue: [VENUE] - Ranked comments I already accept: [PASTE COMMENTS] - Tone: [CIVIL / FIRM] - What would make me reject next round: [MUST FIX] </inputs> <task> Draft an R&R letter: a one-paragraph decision, the must-fix majors, the minors, and what a successful resubmission must show. Every comment must point at the paste. Do not add a paper they must cite unless that paper is already in my pasted comments. </task> <constraints> - Do not invent citations, findings, or a journal rule. - Do not soften [MUST FIX] into optional polish. - Do not promise accept after revision unless I said so. - If a comment in [PASTE COMMENTS] cannot be tied to the manuscript, drop it. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Decision paragraph, numbered majors, numbered minors, resubmission test, UNVERIFIED rows. </format>

💡

Pro tip: Put the two or three must-fix comments at the top. A letter that buries the fatal item under minors wastes a revision cycle.

Draft a Reject With Reasons

22/30

✨ What it does

Claude drafts a reject letter for [PASTE MANUSCRIPT] at [VENUE] with reasons that appear in the paste, not a missing paper Claude invented. You edit the letter, then submit the review.

<context> I am recommending reject. The letter must be specific and fair. Reasons must appear in the paste. Do not invent the paper that would have saved them. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Venue: [VENUE] - Fatal problems I can quote: [PASTE COMMENTS] - What still has value: [STRENGTHS I CAN QUOTE] - Tone: [CIVIL / FIRM] </inputs> <task> Draft a reject letter: the decision in the first paragraph, 2 to 4 reasons tied to quotes, one sentence on what the work still does, and what kind of study (not a title) might belong at this venue later. No invented citations. </task> <constraints> - Do not invent papers, findings, or a comparison article they failed to cite. - Do not pile minors as if they were the reject reason. - Do not insult the authors. - If a reason is not in [PASTE COMMENTS] or the manuscript, drop it. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Decision paragraph, numbered reasons with quotes, one strength sentence, next-study type (not a title), UNVERIFIED rows. </format>

💡

Pro tip: Give reasons the authors can use at the next journal. A reject that invents a literature they missed is a gift to their appeal.

Draft an Accept With Minor Fixes

23/30

✨ What it does

Claude drafts an accept-with-minor-fixes letter on [PASTE MANUSCRIPT] that lists only fixes visible in the paste. You edit the letter, then submit the review.

<context> I am recommending accept with minor fixes. The fix list must be finishable without new data. Do not sneak a major into the minors. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Venue: [VENUE] - Minor fixes I can point at: [PASTE COMMENTS] - Any remaining doubt: [DOUBT OR NONE] </inputs> <task> Draft an accept-with-minors letter: the decision, why the contribution in the paste is enough for [VENUE], and a short fix list. If [DOUBT OR NONE] is a real methods doubt, stop and say this should be R&R instead of dressing it as a typo. </task> <constraints> - Do not invent citations or findings. - Do not add a new analysis as a minor. - Do not invent a journal style rule I did not paste. - If a listed fix cannot be done from the current paste, retag it MAJOR and abort accept. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Decision paragraph, contribution sentence from the paste, numbered minors, abort-to-R&R note if needed, UNVERIFIED rows. </format>

💡

Pro tip: If a fix needs new data, it is not a minor. Move it to R&R instead of hiding it in an accept letter.

Write Editor Notes to Authors

24/30

✨ What it does

Claude writes editor notes to authors on [PASTE MANUSCRIPT] that reconcile [PASTE REVIEWER REPORTS] without adding a finding they did not write. You edit the notes, then submit the review.

<context> I am writing the editor note that sits above the reviewer reports. Reconcile conflicts from the reports I pasted. Do not add a finding a reviewer did not write. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Reviewer reports: [PASTE REVIEWER REPORTS] - My decision: [R&R / REJECT / ACCEPT MINOR] - Venue: [VENUE] - Conflicts I already see: [CONFLICTS OR FIND THEM] </inputs> <task> Write editor notes to the authors: the decision, which comments are required, which are optional, and how to handle conflicts in [PASTE REVIEWER REPORTS]. Quote the reviewers. Do not invent a third report. </task> <constraints> - Do not invent a reviewer comment that is not in the paste. - Do not invent a citation to break a tie. - If two reviewers contradict and I did not pick a side, say so and pick from the manuscript, not from a paper I recall. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Editor note, required vs optional table, conflict rulings, UNVERIFIED rows. </format>

💡

Pro tip: Name which reviewer you are following when they conflict. A blended comment with no owner is how authors fix the wrong thing.

Calibrate Decision Against Venue Rules

25/30

✨ What it does

Claude calibrates a decision on [PASTE MANUSCRIPT] against [VENUE CRITERIA] you pasted and will not invent a journal rule. You edit the decision, then submit the review.

<context> I need to match my decision to the venue's own bar, not a generic prestige bar. Use only rules I paste. Do not invent a journal criterion. </context> <inputs> - Manuscript: [PASTE MANUSCRIPT] - Venue criteria or reviewer form: [VENUE CRITERIA] - My draft comments: [PASTE COMMENTS] - Draft decision: [R&R / REJECT / ACCEPT MINOR / UNDECIDED] </inputs> <task> Score [PASTE MANUSCRIPT] against each line in [VENUE CRITERIA]. For each line: met / not met / not in paste. Then say whether [R&R / REJECT / ACCEPT MINOR / UNDECIDED] still holds. If the draft decision is harsher or softer than the criteria, say so and propose the closer call. </task> <constraints> - Do not invent a venue rule I did not paste. - Do not invent a comparison paper from this journal. - If a criterion is not in the paste, write NEED CRITERION, do not guess. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Criteria table, verdict on the draft decision, closer-call paragraph, UNVERIFIED rows. </format>

💡

Pro tip: Paste the venue's aims and scope or reviewer form. A generic top journal bar will reject work this venue asked for.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Author Response

5 prompts

Map Comments to a Revision Plan

26/30

✨ What it does

Claude maps [PASTE COMMENTS] onto [PASTE MANUSCRIPT] as a revision plan and marks any reply that still needs a source you must find. You edit the response, then submit the review.

<context> I have reviewer or editor comments and the manuscript they point at. I need a revision plan, not a finished reply. Do not invent sources to look responsive. </context> <inputs> - Comments: [PASTE COMMENTS] - Manuscript: [PASTE MANUSCRIPT] - Changes I already made or will make: [PASTE REVISION PLAN OR NONE] - Venue: [VENUE] </inputs> <task> Map each comment to: agree and change, ask for clarification, or decline with evidence already in [PASTE MANUSCRIPT]. Describe the change from [PASTE REVISION PLAN OR NONE] or write NOT YET DONE. If a reply needs a new source, write I MUST FIND A SOURCE, do not invent one. </task> <constraints> - Do not add papers the comments "reminded you of." - Do not claim a change that is not in the plan. - Do not treat every comment as law if it contradicts the pasted evidence. Say so. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Comment table (comment, decision, change or NOT YET DONE, FIND A SOURCE). Then UNVERIFIED rows. </format>

💡

Pro tip: If you have not made the change yet, say NOT YET DONE in the plan. A response that claims edits you did not make is worse than a late reply.

Draft Point-by-Point Replies

27/30

✨ What it does

Claude drafts point-by-point replies to [PASTE COMMENTS] using only changes present in [PASTE REVISION PLAN]. You edit the response, then submit the review.

<context> I need a calm, point-by-point author response that reports changes I actually made or planned, from [PASTE REVISION PLAN]. Do not invent a citation to satisfy add literature. </context> <inputs> - Comments: [PASTE COMMENTS] - Revision plan or changed passages: [PASTE REVISION PLAN] - Venue or course: [VENUE] - Tone: [CIVIL / FIRM] </inputs> <task> For each comment: quote the comment, state agree / clarify / decline, describe the change in [PASTE REVISION PLAN] or say NOT YET DONE, and draft the response sentence. If a reply needs a new source, write I MUST FIND A SOURCE. </task> <constraints> - Do not claim a change that is not in the plan. - Do not invent citations to satisfy "add literature." - Do not insult the reviewer. - Decline only when the pasted evidence cannot support the requested claim, and say so plainly. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Numbered responses. Each: comment, decision, change, reply text. Then UNVERIFIED rows. </format>

💡

Pro tip: Quote the reviewer, then the change. A reply that only says we agree is how a second-round review repeats the same comment.

Decline a Comment You Can Defend

28/30

✨ What it does

Claude drafts a decline of one comment in [PASTE COMMENTS] when [PASTE MANUSCRIPT] already answers it, with no invented citation. You edit the response, then submit the review.

<context> One reviewer comment is wrong or cannot be done given the pasted evidence. I need a polite decline, not a fight. Do not invent a paper that would win the argument. </context> <inputs> - The comment I may decline: [PASTE ONE COMMENT] - Manuscript evidence I already have: [PASTE MANUSCRIPT] - Why I think I can decline: [MY REASON] - Venue: [VENUE] </inputs> <task> Draft a decline: quote the comment, show the pasted evidence that already answers it or shows why the request cannot be met, and offer a smaller change if one exists. If my reason is stronger than the paste, weaken the decline or switch to NOT YET DONE, FIND A SOURCE. </task> <constraints> - Do not invent citations, findings, or a methods precedent. - Do not mock the reviewer. - If the paste does not support a decline, say so and draft an agree-and-change instead. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Quoted comment, evidence lines, decline draft, fallback agree draft, UNVERIFIED rows. </format>

💡

Pro tip: Decline one comment, not the whole report. A defensive letter that rejects every point will get a reject.

Write a Cover Letter After Revision

29/30

✨ What it does

Claude writes a post-revision cover letter from [PASTE MANUSCRIPT] and [PASTE REVISION PLAN] that claims only changes you actually made. You edit the response, then submit the review.

<context> I need a short cover letter after revision. No sales fiction and no invented papers in the journal. Claim only changes that appear in my plan. </context> <inputs> - Revised manuscript or summary: [PASTE MANUSCRIPT] - Revision plan: [PASTE REVISION PLAN] - Venue: [VENUE] - Editor's last note if I have it: [PASTE EDITOR NOTE OR NONE] - Required statements: [ETHICS / CONFLICTS / NONE] </inputs> <task> Draft a cover letter: what the paper is, what we changed (only from [PASTE REVISION PLAN]), how we handled the editor note if pasted, and any required statements I listed. Do not claim fit from papers I did not name. </task> <constraints> - Do not invent similar papers in the journal. - Do not invent an editor's name. - Do not claim a change that is not in the plan. - Do not add citations unless I pasted them for the letter. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Cover letter, then a list of claims in the letter that I must still verify, then UNVERIFIED rows. </format>

💡

Pro tip: Write why this venue still fits in your own words. Claude cannot see the journal's last issue or the editor's last note unless you paste it.

Check the Response Against Changes

30/30

✨ What it does

Claude checks [PASTE AUTHOR RESPONSE] against [PASTE COMMENTS] and flags any reply that claims a change not in [PASTE REVISION]. You edit the response, then submit the review.

<context> I need an honesty pass on an author response I already drafted. Does each reply match a change I can show? Do not invent the missing edit. </context> <inputs> - Author response draft: [PASTE AUTHOR RESPONSE] - Original comments: [PASTE COMMENTS] - Revised passages or plan: [PASTE REVISION] </inputs> <task> For each comment: tag REPLY MATCHES CHANGE, REPLY OVERCLAIMS, or COMMENT UNANSWERED. Quote the change in [PASTE REVISION] for MATCH. For OVERCLAIMS, rewrite the reply so it only claims what is in the revision. For UNANSWERED, draft a honest stub or NOT YET DONE. </task> <constraints> - Do not invent a change that is not in [PASTE REVISION]. - Do not invent a citation to close an unanswered comment. - Do not treat a planned change as done. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Table: comment | tag | quoted change or none | rewritten reply. Then UNVERIFIED rows. </format>

💡

Pro tip: Read the response next to the diff, not next to your memory. Claimed edits you cannot point at are how second-round reviews turn hostile.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

No. Claude can draft a first read, numbered comments, a methods block, and a decision letter from a manuscript you paste. You edit every comment, you own the recommendation, and you submit the review through the journal or course portal. Signing a report you did not check is an integrity problem, not a shortcut.
It will if you let it. These prompts forbid invented papers, authors, years, DOIs, quotations, n, and findings that are not in the paste. If a count or cite is missing, the draft should say NOT IN PASTE or UNVERIFIED. You add the source or you ask the authors. You edit the report, then submit the review.
This page writes a reviewer report from a pasted manuscript: first read, majors, minors, methods critique, a decision letter, and an author-response map. The academic writing page drafts prose you can defend. The literature review page scopes a field and synthesizes papers you pasted. Use those pages to write. Use this page to referee.
Follow the policy in front of you: the reviewer form, the editor's AI note, or the course integrity rules. Drafting help is often allowed when you still own the judgment and you invent no sources. Hidden ghost-reviewing and fake citations are not. When the policy is silent, ask the editor before you submit.
Yes. Set [VENUE] to COURSE or CONFERENCE and paste the rubric or reviewer form you actually have. Do not let Claude invent a page limit, a reject reason, or a citation the manuscript never used. You edit the comments, then submit the review in the portal your instructor or chair named.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.