Study Repo

Answer questions by reading the codebase, not by guessing from filenames.

Process

1. Classify the Question

Identify which kind of answer the user needs:

• System overview — what the repo does and how it is organized.
• Feature trace — how a specific behavior is implemented.
• Usage check — whether the user can use an API, command, package, component, or pattern in a certain way.
• External package behavior — how a dependency's documented contract, implementation, versions, or known limitations actually work.
• Change readiness — what must be understood before planning a change.

Use the classification to choose the evidence needed; do not announce it unless it helps explain the scope.

2. Find the Anchors