Codebase questions for engineers new to a repo
New engineers ask an agent where things live and how flows work, getting answers with file references instead of waiting on a teammate.
The use case
Joining a team or picking up an unfamiliar service means days of asking where things are. Anthropic describes its own new hires using Claude Code to explore the codebase, trace how a request moves through services, and find the right files before touching anything. Tools such as Amp do the same across large repositories. The agent searches and reads the code, then answers with file paths and short explanations. The engineer still opens the referenced files to confirm the answer, and checks anything important with the code owner, since the agent can describe old patterns that the team has moved away from.
Example workflow
- Open the repository in the agent and ask a broad orientation question
- Ask follow-ups about specific flows, data models or configs
- Open the cited files to confirm
- Write down confirmed findings in onboarding notes
- Check uncertain answers with a code owner
Tools
- Claude Code
- Amp
Risks and guardrails
- Answers can describe deprecated code paths as current
- Agent may guess when code is generated or external; ask for file references
- Keep read-only mode while exploring
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Claude: how Anthropic teams use Claude Code: claude.com/resources/articles/how-anthropic-teams-use-claude-code
- Amp docs: ampcode.com/docs