Developer Tools & Code Intelligence · core
Repository Intelligence
Structure, symbols, history, ownership, conventions, architecture, semantic search, and change-aware retrieval.
Mental model
Repository intelligence answers what exists, why it exists, who depends on it, and what changed. It combines indexed code, graphs, history, and local instructions.
How to study Repository Intelligence
Begin by restating the mental model in your own words, then connect it to a concrete system you have built or operated. Name the mechanism, the constraint it addresses, and the trade-off it introduces. Use GitHub Code Search Syntax, Software Engineering at Google — Ch. 17: Code Search, Regular Expression Matching with a Trigram Index (Russ Cox) to check details, but close the source before writing your explanation. Retrieval is the learning step; rereading is only preparation.
Next, compare Repository Intelligence with Dependency & Blast-radius Analysis, IDE & CLI Tooling. Ask what changes in correctness, latency, resource use, operability, and failure recovery. Complete Design exercise: Repository Intelligence and preserve the command, input, output, and one failed attempt as evidence. Finish by explaining the idea without jargon to someone who has not studied the track.
Proof of understanding
- Explain the mechanism from first principles and identify the state it reads or changes.
- Give one situation where the concept is the right choice and one where it is not.
- Predict a realistic failure mode before running the drill, then compare the prediction with evidence.
- Connect the result to a roadmap or build artifact instead of treating the concept as isolated trivia.
Learn from primary sources
Practice and explain it back
Design exercise: Repository Intelligence
Structure, symbols, history, ownership, conventions, architecture, semantic search, and change-aware retrieval. Implement designOutline() returning non-empty values for: index, retrieval, contextAssembly. Each value must name a concrete mechanism or decision.
Expected evidence: A design outline with index, retrieval, contextAssembly plus an explicit failure mode or trade-off.
Open the interactive drill →Review prompts
- Why is embedding-based semantic search insufficient on its own for repository questions?
Build evidence
Synthesize: Developer Tools & Code Intelligence
Build repository-aware tools that analyze, test, review, debug, and safely remediate code. Produce one working system, benchmark, or evidence-backed design that integrates the path.
- Implements or precisely models the core mechanisms from all three milestones
- Includes at least one injected failure or adversarial case and demonstrates recovery
- Reports quality, latency, resource, reliability, or usability measurements relevant to the domain
- Ships a concise architecture note explaining decisions, trade-offs, and remaining risks