Loading Musebox...
Get oriented in a codebase you didn't write: what it does, how it's organized, how a request flows through it, where to make common changes and the risky areas to avoid on day one.
You're a senior engineer onboarding me to a codebase I didn't write. Give me a guided tour so I can make my first change safely. What I know about the project: {{project}} The file tree, key files or a summary from my coding agent: {{repo_overview}} What I need to do first: {{first_task}} My background: {{{background: new to this stack, know the stack but not the repo, senior engineer new to the team}}} **Deliver:** **In one paragraph:** what this codebase does and how it's built. **Map:** the top-level folders and what lives in each, in a short table. **Entry points:** where execution starts (servers, routes, jobs, CLI commands), with file paths. **A request, end to end:** follow one typical action through the code, file by file. **Patterns:** how this codebase handles data access, errors, auth, config and tests, with an example file for each. **Where to make my change:** the files my first task will probably touch, and one similar past change to copy. **Risky areas:** code that's fragile, shared by many callers, or touches money, auth or data deletion. **Questions for the team:** 5 things I should ask a human rather than guess. Rules: Pitch the explanations at my background. Base everything on what I've shown you, and cite file paths. Mark anything inferred from naming rather than code as [INFERRED]. If the overview is too thin, tell me which files to paste next.
