Claude Code Prompts

Claude Code works inside your repository, so a prompt for it names files, commands and the definition of done. Each block below is one job: plan a change, add tests, review a diff, fix CI, write the project's CLAUDE.md.

coding
Bug Reproduction Test

I want you to act as a debugger who proves a bug exists before fixing it. I will describe the wrong behaviour, how I triggered it and what I expected, and…

coding
CI Failure Fixer

I want you to act as the engineer on call for a broken build. I will paste the failing job's log between <log> and </log> tags and tell you which branch it is…

coding
CLAUDE.md Writer

I want you to act as a maintainer writing the CLAUDE.md that this repository is missing. That file tells a coding agent how to work here, so everything in it…

coding
CLI Command Builder

I want you to act as an engineer adding a new command to this project's command line tool. I will describe what the command should do and what I want to type…

coding
Codebase Tour Guide

I want you to act as a colleague giving me a tour of a codebase I have never seen. I will tell you what I have been asked to do, so that the tour covers the…

data
Database Migration Writer

I want you to act as an engineer writing a database migration for this repository. I will describe the schema change and tell you roughly how large the…

coding
Dependency Migration Plan

I want you to act as an engineer upgrading a dependency across a major version. I will name the package and the version to move to. Survey first. Find every…

coding
Performance Profiler

I want you to act as an engineer making a slow path faster, using measurements rather than guesses. I will tell you what is slow, how I noticed it, and what…

coding
Pull Request Reviewer

I want you to act as a reviewer of a change in this repository. I will give you what to review: a branch name, a pull request number, or my uncommitted…

coding
Repo Feature Planner

I want you to act as a senior engineer who plans a change in my repository before writing any code. I will describe the feature in one paragraph, and you have…

coding
Safe Refactor Pass

I want you to act as an engineer carrying out a refactor in which behaviour must not change. I will name the file, module or pattern to clean up and say why it…

coding
Security Review Pass

I want you to act as a security reviewer looking at a change in this repository. I will give you what to review: a branch, a pull request number, or my…

Claude Code Prompts: questions people ask

Do I paste these in the terminal or into the Claude app?

In the terminal, with Claude Code started in the repository root, because every block assumes it can read files, run your tests and report real paths. Codebase Tour Guide means nothing without that access. The chat app can still help with a single file you attach, but drop the lines about exploring first and naming what it read.

How do I stop it editing files before I have agreed the plan?

Repo Feature Planner tells it to explore, list the files it read and write nothing during that step, then return commit sized pieces each with the test that proves it. Read the plan, correct whatever is wrong about your codebase, and only then say go. Planning in one session and implementing in the next makes that boundary harder to cross by accident.

What stops it turning a red build green by deleting the failing test?

CI Failure Fixer forbids it outright and makes it classify the failure first: a genuine defect, a flaky test, an environment or dependency problem, or broken pipeline configuration. It also has to quote the first real error rather than the last line printed, and reproduce the failure locally before touching code. If everything passes locally, the gap between environments is the bug.

Do I need a CLAUDE.md in the repo before any of this works?

No, although later runs go better with one. CLAUDE.md Writer reads your build files, scripts, test configuration, CI workflows and recent commits, then records what the project is, the commands it verified, the directory layout and the conventions the code genuinely follows. Where such a file already exists, it keeps whatever still holds instead of starting over.

More prompt collections

Claude Prompts

New prompts in your inbox

One email a week: the best new prompts from the library and one short guide on prompting. No spam, unsubscribe any time.