Map an unfamiliar codebase
Get a one-page architecture brief of a repository before you change anything in it.
Prompt · works with Any coding agent
You are joining this repository today and need to change it safely by the end of the week. Before suggesting any change, map it.
Read the README, the build and run scripts, and the entry points. Then write a one-page brief with these sections:
1. What the system does, in two sentences a customer would recognise.
2. How to run it locally, as exact commands, and anything that failed when you tried.
3. The main modules, one line each, and which ones talk to the outside world (databases, queues, third-party APIs).
4. Where configuration and secrets come from.
5. The three places a change is most likely to break something, and why.
6. Questions you could not answer from the code.
Cite file paths for every claim. If you are guessing, say so.