A coding prompt for explain an unfamiliar codebase. It gives Claude and Cursor a clear role, explicit constraints and a defined output, so the first answer is closer to usable. Fill in the variables, run it once, then use the verification notes on this page to review the result.
4.8(57 ratings)655 copies
Updated By Author
46 words · v1.2
Fill in the blanks · 1 variable
Claude promptReplace every highlighted token before sending
<task>
Explain this codebase to a new contributor. Cover the entry points, data flow, main modules, external services, build and test commands, and the three most surprising design decisions. Use a diagram in text if helpful. Cite file paths. End with five good first tasks.
Files:
{files}
</task>
Think carefully before answering. Keep any reasoning separate and put the final deliverable inside <answer> tags.
Share what worked, what broke and which model you used. Comments appear after posting and are moderated for spam.
How to use this prompt
1
Open Claude and start a new chat. Paste the prompt exactly as written.
2
Replace each placeholder ({files}) with your own details. Leave the instructions and the output format untouched.
3
Add one concrete example or data point if the model's first answer is vague. Specific input produces specific output.
4
Run it once, then ask for a single revision with a specific critique rather than regenerating from scratch.
5
Review the result. Reproduce the bug, review the diff and run the tests in a clean environment.
Worked example
This is the kind of input the prompt expects and the shape of output it produces. Your result will differ with the model and the details you supply.
Example input
Files: your files
Example output
**Diagnosis:** the handler reads `req.body` before the JSON middleware runs, so the body is undefined on POST requests.
**Fix:** move the middleware above the route registration and add a guard for missing bodies. No public API changes.
**Verification:** added a failing test for an empty JSON body, confirmed it fails, applied the fix, then ran the full suite. The test now passes and the unrelated snapshot tests are unchanged.
Tips for a better result
Paste the full error and the smallest relevant code, not a screenshot of the stack trace.
Ask for a plan before allowing multi-file edits; it prevents sprawling refactors.
Require a failing test first and a verification command at the end.
Change one variable at a time and compare the outputs; it is the fastest way to learn what this model responds to.
Common mistakes
Accepting a confident fix without reproducing the bug or running tests.
Letting the assistant rewrite entire files when a three-line diff would do.
Pasting secrets, tokens or customer data into a hosted model.
Verified Knowledge · FAQ
Questions about this prompt
Practical answers about running the explain an unfamiliar codebase prompt.
Related prompts
Same job, a different angle — or the next step in the workflow.
This copy-ready coding prompt helps you plan a zero-downtime deployment with fewer blank-page decisions. Paste it into Claude and ChatGPT, fill the variables, and you get a structured first draft you can edit. It is written for repeatable results and tells you what to check before publishing.
Write a technical design document with a prompt built for Claude and ChatGPT. It supplies context, constraints and an output contract, then asks the model to surface assumptions and gaps. Copy it, fill the variables and treat the result as a structured draft, not a final answer.
Generate unit tests that fail before the fix with a prompt built for Cursor and Claude. It supplies context, constraints and an output contract, then asks the model to surface assumptions and gaps. Copy it, fill the variables and treat the result as a structured draft, not a final answer.
CursorClaudeGitHub Copilot
4.7(77)695 copies
A
Written and reviewed by Author
AIPrompt123 Contributor
Contributing author and prompt engineer at AIPrompt123.
Last reviewed 19 February 2026 · version 1.2 · tested on Claude, Cursor
Comments
Share what worked, what broke and which model you used. Comments appear after posting and are moderated for spam.