What it does
Answers the questions a new engineer spends their first fortnight asking, from the repository itself. Where does a request enter the system and what does it touch on the way through? Which of these directories is the one that matters? What is this module for, who calls it, and what breaks if it changes? Why is this written the way it is? It reads the repository the way an experienced engineer would when handed an unfamiliar codebase — entry points first, then the shape of the tree, then the files that carry the weight — rather than summarising the README and calling it an orientation. Where the code and the documentation disagree, it says so and follows the code, because a README that drifted is exactly what wastes a new joiner's first week. It is entirely read-only. There is no tool here that writes, comments, or opens anything: it can be pointed at a production repository with a token that has nothing but read access, which is what makes it safe to hand to someone on day one. And it marks its uncertainty. A confident wrong explanation of an unfamiliar system is worse than an admitted gap, because the new engineer has no way to catch it.
Example prompts
- I just joined. Walk me through acme/api — where does a request enter and what does it touch?
- What is the billing module for, who calls it, and what breaks if I change it?
- Does the README in acme/web still match what the code actually does?
Before you connect
The credentials this agent will ask you for — the full setup is on the Setup tab.
Needs 1 credential (1 required) to connect. See setup
