CodeHub

Verify Api

CALL BEFORE writing code that uses a third-party library: returns the CURRENT signature, doc and location of a symbol from the library's indexed source — the fast check that an API you remember still exists in that form. Training-data knowledge of libraries is often stale; this is ground truth with provenance. `package` can be a bare name ('fastmcp', 'pydantic-ai') or 'owner/repo'.

Usage Examples

CALL WHEN unsure how to use a library correctly: real, current call sites of the package (or one of its symbols) pulled from repos that actually depend on it — ground truth beats guessed usage. Each example cites repo@version · file:line.

Whats New

CALL WHEN asked what changed recently in a library, or before adopting a new release: the library's own CHANGELOG as shipped at the INDEXED version (version-pinned — web docs only show latest), plus whether a newer release exists.

Api Changes

CALL WHEN code broke after a dependency upgrade (or before upgrading): diffs a library's API between two versions — symbols added/removed and every changed signature (old → new). Versions default to the two most recent indexed; asking for a version that isn't indexed yet starts indexing it in the background (1–5 min) — call again shortly for the diff.

Find Repos

START HERE when you need a library/tool/example and don't know the repo: routes a plain-language need (topic, purpose, language) to the best-matching indexed repos across the whole hub, ranked. Returns graph ids for the per-graph tools.

Similar Repos

Alternatives / prior art: repos most similar to a given one by description, code vocabulary and shared dependencies — works across languages. Use for 'libraries like X' or to survey how others solved the same problem.

Dependents

Who ACTUALLY uses a package — every indexed repo that declares a dependency on it (hub-wide reverse lookup). Use to find real-world usage to learn from, or to gauge adoption before choosing a library.

List Graphs

Every indexed graph (repo@version) — a very large dump; prefer find_repos() to locate repos by need. Pass a slug (or 'owner/repo') as `graph` to the per-graph tools.

Explore

PRIMARY TOOL for a repo — call FIRST for almost any question about how its code works, and before writing code that imitates or calls it. Give the symbol/file names spanning what you care about; a plain question works too, but NAMING THE SYMBOLS is markedly more accurate. ONE call returns: verbatim current source of the relevant symbols grouped by file, the call path among them, interface -> implementation hops a text search cannot follow, callers outside the set, and which symbols have no cove

Search

Locate a NAME in a repo — pointers only, no source: symbol names, signatures, DOC COMMENTS, paths. Cheap, so issue several refined queries. To UNDERSTAND a mechanism rather than locate a name, call explore() — same index, but it returns the code and the flow in one call.

Symbol Context

Deep dive on ONE symbol (follow-up to explore, which covers several related symbols and the flow between them in a single call): definition + doc + source + callers + callees + implementers + tests for a symbol. Prefer this over stitching the answer from separate calls.

Read

Read a repo's code — use INSTEAD of guessing from memory before you write code that calls it. `target` is a SYMBOL NAME (that symbol's verbatim, hash-verified source) or a FILE PATH (line-numbered, start/end honoured like Read). `symbols_only=True` on a path returns the file's symbol map instead of its source. Replaces the former load_source / read_file / list_symbols tools; for several related symbols use explore().

Grep

Regex across ALL stored source + config of a repo. ESPECIALLY: paste a library's error message here to find where it's raised and what condition triggers it.

Callers

Who calls a symbol, what it calls, or what implements it. direction="in" (default) callers, confidence-scored with interface contracts expanded; "out" callees; "implements" the concrete types satisfying an interface/func-type contract — the dynamic-dispatch hops grep cannot follow. Absorbs the former implementers tool. Use before changing or imitating an API to see real call patterns.

Impact

Blast radius before a change: confidence-weighted transitive set of what is affected if this symbol changes.

Overview

Orientation when entering an unfamiliar repo: modules, EXTENSION POINTS, entry points, core symbols. Call this first, then search.