Claude Prompt Library

30 Claude Code Prompts for Code Review

30 copy-paste prompts

Point at the diff and the files. Claude Code reviews in that scope, splits blockers from nits, and does not invent a CVE or a score. Not a merge and not a rewrite.

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. Drafted with AI writing assistance and checked against our editorial policy.

By Louis Corneloup · Founder, Techpresso

Last updated September 8, 2026·Drafted with AI assistance (how we make prompts)

Read

5 prompts

Review Diff

1/30

✨ What it does

Claude Code reviews the diff in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a reviewer working in Claude Code. <context> I need you to review this diff in scope. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Review [DIFF] 2. Stay about [FILES] 3. Blockers then nits </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a CVE.

Blockers First

2/30

✨ What it does

Claude Code lists review blockers in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a blocker reviewer working in Claude Code. <context> I need you to list blockers only. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Blockers from [DIFF] 2. Stay about [FILES] 3. Empty is ok </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a blocker.

Nits

3/30

✨ What it does

Claude Code lists review nits in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a nit reviewer working in Claude Code. <context> I need you to list nits only. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Nits 2. Stay about [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Nits are optional.

Ask

4/30

✨ What it does

Claude Code writes reviewer questions in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an ask reviewer working in Claude Code. <context> I need you to questions a reviewer should ask. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Questions from holes 2. Stay about [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent an owner.

Summary

5/30

✨ What it does

Claude Code summarizes the diff in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a summary reviewer working in Claude Code. <context> I need you to summarize what this diff does. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Summary 2. Stay about [FILES] 3. No marketing </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a ticket.

Risk

5 prompts

Security

6/30

✨ What it does

Claude Code does a security review in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a security reviewer working in Claude Code. <context> I need you to security review in scope. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Security from [DIFF] 2. Stay about [FILES] 3. No invented CVE id </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent critical.

Auth

7/30

✨ What it does

Claude Code reviews auth in the diff in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an auth reviewer working in Claude Code. <context> I need you to auth review in scope. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Auth paths 2. Stay about [FILES] 3. No invented role </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent admin bypass.

Data

8/30

✨ What it does

Claude Code reviews data in the diff in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a data reviewer working in Claude Code. <context> I need you to data and PII review in scope. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Data touched 2. Stay about [FILES] 3. UNVERIFIED on missing policy </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent GDPR copy.

Perf

9/30

✨ What it does

Claude Code reviews perf in the diff in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a perf reviewer working in Claude Code. <context> I need you to perf review in scope. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Perf risks from [DIFF] 2. Stay about [FILES] 3. No fake 200ms </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent N+1 if you cannot see it.

Race

10/30

✨ What it does

Claude Code reviews concurrency in the diff in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a race reviewer working in Claude Code. <context> I need you to concurrency review in scope. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Races you can point at 2. Stay about [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a deadlock.

Tests

5 prompts

Missing Tests

11/30

✨ What it does

Claude Code lists missing tests in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a tests reviewer working in Claude Code. <context> I need you to missing tests in this diff. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] - Test: [TEST OR VERIFY] </inputs> <task> 1. Missing cases 2. Test or ask 3. Stay about [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent coverage 80%.

Weak Tests

12/30

✨ What it does

Claude Code flags weak tests in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a weak-tests reviewer working in Claude Code. <context> I need you to weak tests in this diff. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Weak asserts 2. Stay about [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a snapshot rant.

Break

13/30

✨ What it does

Claude Code lists what might break in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a break reviewer working in Claude Code. <context> I need you to what this might break. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Break list from [DIFF] 2. Stay about [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent mobile Safari.

Migrate

14/30

✨ What it does

Claude Code reviews migrations in the diff in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a migrate reviewer working in Claude Code. <context> I need you to review migrations in this diff. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Migrate risks 2. Stay about [FILES] 3. No invented downtime </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent ACCESS EXCLUSIVE.

Flags

15/30

✨ What it does

Claude Code reviews flags in the diff in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a flags reviewer working in Claude Code. <context> I need you to review flags in this diff. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Flags I have: [FLAGS OR NONE] </inputs> <task> 1. Flags or none 2. Stay about [DIFF] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent FLAG_NEW.

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. The library keeps growing.

Try AI Academy Free

Tone

5 prompts

Kind

16/30

✨ What it does

Claude Code writes kind review comments in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a kind reviewer working in Claude Code. <context> I need you to kind review comments. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Kind 2. Specific 3. Stay about [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: No dunk.

Inline

17/30

✨ What it does

Claude Code writes inline review comments in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an inline reviewer working in Claude Code. <context> I need you to inline comments I can paste. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Path and line if you can see them 2. Stay about [FILES] 3. UNVERIFIED on missing lines </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent L142.

Push Back

18/30

✨ What it does

Claude Code writes reviewer push-back in [COMMENT] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a push-back reviewer working in Claude Code. <context> I need you to reviewer push-back I can send. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [COMMENT] - Diff: [DIFF] </inputs> <task> 1. Facts from [DIFF] 2. Kind </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a guide.

LGTM Honest

19/30

✨ What it does

Claude Code says LGTM only if earned in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an lgtm reviewer working in Claude Code. <context> I need you to LGTM only if you mean it. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. LGTM or not 2. Why 3. Stay about [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent LGTM.

Humanize

20/30

✨ What it does

Claude Code humanizes the review in [DRAFT] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a humanizer working in Claude Code. <context> I need you to humanize the review. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DRAFT] - Keep: [KEEP] </inputs> <task> 1. Cut delve 2. Keep [KEEP] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: It should sound like a teammate.

Stop

5 prompts

Ask First

21/30

✨ What it does

Claude Code plans the review then waits in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a plan reviewer working in Claude Code. <context> I need you to plan the review then wait. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Plan only 2. Wait if I want comments later </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not rewrite the diff.

No Rewrite

22/30

✨ What it does

Claude Code skips rewriting the PR in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a rewrite cutter working in Claude Code. <context> I need you to do not rewrite the PR. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Comments only 2. Stay about [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: A rewrite is out of scope.

No Merge

23/30

✨ What it does

Claude Code skips merging in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a merge cutter working in Claude Code. <context> I need you to do not merge. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Review only </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Merge is out of scope.

Scope Only

24/30

✨ What it does

Claude Code reviews only named files in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a scope reviewer working in Claude Code. <context> I need you to review only the files I named. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Only [FILES] 2. Ignore the rest </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Wander is out of scope.

Off Limits

25/30

✨ What it does

Claude Code honors review off limits in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a fence reviewer working in Claude Code. <context> I need you to honor off limits in review. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Off: [OFF] - Files: [FILES] </inputs> <task> 1. Honor [OFF] 2. Stay in [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Off limits stays off.

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

AI Academy: hands-on tutorials on Claude, ChatGPT, Midjourney, and many other AI tools. New tutorials are added regularly.

Start Your Free Trial

Fixes

5 prompts

Shorter

26/30

✨ What it does

Claude Code shortens the review in [DRAFT] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a cutter working in Claude Code. <context> I need you to shorter review. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DRAFT] - Cap: [CAP] </inputs> <task> 1. Under [CAP] 2. Keep blockers </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Cut the essay.

Review Plus Tests

27/30

✨ What it does

Claude Code reviews plus missing tests in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a combo reviewer working in Claude Code. <context> I need you to review plus missing tests. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Review 2. Missing tests </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Tests stay a list.

Review Plus Security

28/30

✨ What it does

Claude Code reviews plus security notes in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a combo reviewer working in Claude Code. <context> I need you to review plus security notes. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Files: [FILES] </inputs> <task> 1. Review 2. Security </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: No invented CVE.

Unverified Review

29/30

✨ What it does

Claude Code tags invented review claims in [DRAFT] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an honesty reviewer working in Claude Code. <context> I need you to tag invented review claims. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DRAFT] - Diff: [DIFF] </inputs> <task> 1. Tag extras 2. Keep what the diff shows </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Drop invented vulns.

Checklist

30/30

✨ What it does

Claude Code fills our review checklist in [CHECKLIST] [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a checklist reviewer working in Claude Code. <context> I need you to fill our review checklist. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHECKLIST] [DIFF] - Files: [FILES] </inputs> <task> 1. Fill from [DIFF] 2. Empty stays empty </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a check.

Free tool

Prompt Optimizer

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

Try it free →

Frequently Asked Questions

They are written for Claude Code in the terminal: plan, edit, test, and stay inside code review. You can paste a shorter version into claude.ai if you are not in a repo.

Each prompt sets scope and non-goals. Still use Plan mode on multi-file work, and read the diff before you accept edits.

It helps. A short CLAUDE.md with stack, test command, and files Claude must not touch keeps these prompts from inventing a second style guide.

The prompts are free to copy. Claude Code needs your Anthropic login and uses your plan's usage. Local files never leave your machine except through that session.

The hub is a 21-prompt overview. This page is only code review: thirty copy-paste jobs with scope, verify, and non-goals already written.

Prompts are the starting line. Tutorials are the finish.

A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.

Start 7-Day Free Trial Explore AI for Entrepreneurs

7-day free trial. Cancel anytime.

Browse All Claude Prompt Collections Browse All Prompt Collections

Popular prompt collections

AI Photo Editing Prompts ChatGPT Jailbreak Prompt Best ChatGPT Prompts Funny Hinge Prompts ChatGPT Caricature Prompts