Claude Prompt Library

30 Claude Code Prompts for Pull Requests

30 copy-paste prompts

Point at the diff and the files. Claude Code writes titles, bodies, and replies from that and does not invent reviewers, checks, or tickets. Not a merge bot.

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.

By Louis Corneloup · Founder, Techpresso

Last updated September 8, 2026·Hand-curated & tested by the AI Academy team

Write

5 prompts

PR Body

1/30

✨ What it does

Claude Code writes the PR body 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 pr writer working in Claude Code. <context> I need you to write the PR body from 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] - Ticket: [TICKET OR NONE] </inputs> <task> 1. Body from [DIFF] 2. Ticket or skip 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 JIRA-123.

Title

2/30

✨ What it does

Claude Code writes the PR title 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 title writer working in Claude Code. <context> I need you to write the PR title. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Style: [STYLE OR VERIFY] </inputs> <task> 1. Title from [DIFF] 2. Style or ask </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 feat: if we do not use it.

Commits

3/30

✨ What it does

Claude Code messages the commits 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 commit writer working in Claude Code. <context> I need you to split or message commits as I asked. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Rule: [RULE] - Files: [FILES] </inputs> <task> 1. Honor [RULE] 2. Stay in [FILES] 3. No invented trailers </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 Co-authored-by.

Test Plan

4/30

✨ What it does

Claude Code writes the PR test plan 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 test-plan writer working in Claude Code. <context> I need you to write the test plan I can run. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Test: [TEST OR VERIFY] </inputs> <task> 1. Plan from what changed 2. Test or ask </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 npm test.

Screenshots Note

5/30

✨ What it does

Claude Code lists owed screenshots 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 screens writer working in Claude Code. <context> I need you to say which screenshots I still owe. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - UI files: [UI OR NONE] </inputs> <task> 1. Owe list 2. UI or skip </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 shot.

Risk

5 prompts

Risks

6/30

✨ What it does

Claude Code lists PR risks 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 risk writer working in Claude Code. <context> I need you to list PR risks from the 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. Risks from [DIFF] 2. Stay about [FILES] 3. No fake Sev-1 </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 production impact.

Rollback

7/30

✨ What it does

Claude Code writes PR rollback 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 rollback writer working in Claude Code. <context> I need you to write rollback for this PR. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - How we ship: [SHIP OR VERIFY] </inputs> <task> 1. Rollback from [SHIP] or ask 2. Stay about the 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 helm.

Flags

8/30

✨ What it does

Claude Code notes PR flags 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 writer working in Claude Code. <context> I need you to note flags this PR needs. 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.

Migrate

9/30

✨ What it does

Claude Code calls out PR migrations 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 writer working in Claude Code. <context> I need you to call out migrations in this 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. Migrations only if present 2. Order [VERIFY] </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 migrate command.

Secrets Hunt

10/30

✨ What it does

Claude Code hunts secrets in 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 secrets hunter working in Claude Code. <context> I need you to hunt secrets in this 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. Hunt in [DIFF] 2. Stay in [FILES] 3. Do not print a secret you find. Say the path. </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 key.

Review

5 prompts

Reply

11/30

✨ What it does

Claude Code replies to the review comment 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 reply writer working in Claude Code. <context> I need you to reply to this review comment. 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] - Files: [FILES] </inputs> <task> 1. Reply from facts 2. Stay in [FILES] 3. No invented fix time </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 I will ship Friday.

Nit Sort

12/30

✨ What it does

Claude Code sorts nits vs blockers in [COMMENTS] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a nit sorter working in Claude Code. <context> I need you to sort nits vs blockers. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [COMMENTS] - Files: [FILES] </inputs> <task> 1. Sort 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 blocker.

Push Back

13/30

✨ What it does

Claude Code pushes back with facts 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 writer working in Claude Code. <context> I need you to push back with facts. 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 3. No dunk </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 style guide.

Accept

14/30

✨ What it does

Claude Code accepts and plans the fix in [COMMENT] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an accept writer working in Claude Code. <context> I need you to accept and plan the fix. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [COMMENT] - Files: [FILES] </inputs> <task> 1. Accept 2. Plan in [FILES] 3. Wait for GO if I said plan 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: Do not edit until I say.

Summary

15/30

✨ What it does

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

You are a summary writer working in Claude Code. <context> I need you to summarize review threads. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [THREADS] - Files: [FILES] </inputs> <task> 1. Summary from [THREADS] 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 thread.

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

Ship

5 prompts

Draft Vs Ready

16/30

✨ What it does

Claude Code labels draft or ready 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 ready writer working in Claude Code. <context> I need you to say draft or ready from the diff. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Missing: [MISSING OR NONE] </inputs> <task> 1. Draft if [MISSING] 2. Else ready 3. 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 CI is green.

Reviewers

17/30

✨ What it does

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

You are a reviewers writer working in Claude Code. <context> I need you to suggest reviewers I named. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [PEOPLE] - Diff: [DIFF] </inputs> <task> 1. Only [PEOPLE] 2. Why from [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 @alice.

Labels

18/30

✨ What it does

Claude Code applies labels I have in [LABELS] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a labels writer working in Claude Code. <context> I need you to apply labels I have. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [LABELS] - Diff: [DIFF] </inputs> <task> 1. Only [LABELS] 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 urgent.

Changelog

19/30

✨ What it does

Claude Code writes a changelog line 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 changelog writer working in Claude Code. <context> I need you to write a changelog line. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Style: [STYLE OR VERIFY] </inputs> <task> 1. Line from [DIFF] 2. Style or ask </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 Keep a Changelog if we do not use it.

Release Note

20/30

✨ What it does

Claude Code writes a user-facing note 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 release writer working in Claude Code. <context> I need you to write a user-facing note. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - What users see: [SEE OR NONE] </inputs> <task> 1. Note from [SEE] or skip if 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 a marketing sentence.

Stop

5 prompts

Ask First

21/30

✨ What it does

Claude Code plans the PR text 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 writer working in Claude Code. <context> I need you to plan the PR text 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 for GO </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 open the PR until I say.

No Force

22/30

✨ What it does

Claude Code avoids a force push 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 force cutter working in Claude Code. <context> I need you to do not force push unless I said. 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. Normal commits 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: Force push is out of scope.

No Merge

23/30

✨ What it does

Claude Code does not merge 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 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. Text 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: Merge is out of scope.

Match Template

24/30

✨ What it does

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

You are a template writer working in Claude Code. <context> I need you to fill our PR template. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [TEMPLATE] [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 checkbox.

Off Limits

25/30

✨ What it does

Claude Code honors PR 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 writer working in Claude Code. <context> I need you to honor off limits in 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] - 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: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Fixes

5 prompts

Undo Wander

26/30

✨ What it does

Claude Code reverts extra PR 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 writer working in Claude Code. <context> I need you to revert extra PR files. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Allowed: [FILES] </inputs> <task> 1. Revert extras 2. Keep the PR change </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: Neighbors stay.

PR Plus Tests

27/30

✨ What it does

Claude Code writes PR body plus test plan 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 writer working in Claude Code. <context> I need you to PR body plus test plan. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Test: [TEST OR VERIFY] </inputs> <task> 1. Body 2. Test plan </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: Test plan stays runnable.

PR Plus Risks

28/30

✨ What it does

Claude Code writes PR body plus risks 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 writer working in Claude Code. <context> I need you to PR body plus risks. 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. Body 2. Risks </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: Risks stay real.

Humanize

29/30

✨ What it does

Claude Code humanizes the PR body 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 PR body. 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 an engineer.

Shorter

30/30

✨ What it does

Claude Code shortens the PR body 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 PR body. 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 risks </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 novel.

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 pull requests. 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 pull requests: 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 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

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