io.github.aahlijia/dekko

Anchor a durable note to a symbol. Notes are committed to .dekko/notes.json and shown on the symbol's card and in its context pack. Use after a non-obvious change so the rationale survives.

Repo-wide resolver-trust summary: total ambiguous call sites, the ambiguous rate, and the top colliding names/files. Run this before leaning on get_callers/get_callees/workset for an impact-analysis decision on a repo with generic/common method names — a low ambiguous rate means the call graph is trustworthy as-is; a high one concentrated in a few files means spot-check those files' call sites by hand before trusting the graph there.

Every function/method that uses a type as a parameter or return type — for 'what breaks if I change this struct/class's shape' questions the call graph alone can't answer, since a function can use a type without calling anything on it. Matches the bare type name inside wrapper syntax (Optional[Config], Vec<Config>, Config | None all match 'Config') unless exact=true. Only functions/methods carry typed params/returns — struct/class fields typed with the target type are not covered.

List the symbols that reference an external (out-of-repo) name, e.g. a stdlib or third-party function, with call sites — one call gets every real call site across the repo, where grepping the bare name also pulls in imports, comments, and unrelated same-named locals you'd have to hand-filter.

Every in-repo symbol a symbol calls (set sites=true for call-site lines) — what this code depends on, without reading its body. Walks the resolved call graph directly instead of grepping the body for names that look like calls.

Every symbol (and module-level site) that calls a symbol — exact call edges, unlike grep, which can't tell a call from a same-named string. Set sites=true for the precise path:line of each call. Use for impact analysis before a change. Test-file callers are excluded by default — set include_tests=true to see them.

Compact signature neighborhood (callers/callees within N hops) for editing a symbol or file. Token-budgetable. Example: target="awardXp", task="who calls this".

What extends, implements, or is impl'd for a class/interface/struct/trait — the 'if I change this, who's affected' blast-radius question for type declarations. Set transitive=true for every direct and indirect implementor, not just direct ones. Does not include each implementor's own callers — pair with get_callers on individual results for that. Test-file subtypes are excluded by default — set include_tests=true to see them.

What a class/interface/struct/trait extends, implements, or is impl'd for — its own declared heritage. Set transitive=true for the full ancestor chain/DAG (multiple inheritance and multi-interface implementation both fan out, not a single line). Covers Python/JavaScript/TypeScript/Java/Rust/C++. Go struct embedding is not extracted (only answers composition, not interface satisfaction, so not worth the confusion) and Go's structural interface satisfaction has no declaring syntax to extract at all — no tree-sitter query can see it.

Test files a runner should exercise after a change: reverse call-graph reachability from changed symbols plus an import-edge fallback (leads, not verdicts — static analysis misses fixtures and dynamic dispatch). More reliable than grepping test files for the changed symbol's name, which misses indirect callers and matches unrelated same-named text.

List notes anchored to a symbol, or every note in the repo when no symbol is given.

Report whether map.json is fresh or stale.

A file's (or directory's) structural outline — signatures + doc lines, no bodies — at roughly a tenth the cost of reading it. Prefer this before reading a file to learn what it contains.

Signature, kind, location, doc, fan-in/out, and notes for one symbol — the fast way to learn what a symbol is without reading its file.

Regenerate the map; set full=true to ignore the cache and re-parse every file.

Rank symbols by free-text relevance to a natural-language description — for when you know what the code should do but not its name. Matches against names, signatures, and doc lines with BM25-style scoring, not substring matching. Falls back to zero hits (not an error) when nothing matches; try broader or different terms. Use query_symbol/get_callers instead once you have an exact name.

Compact repo digest (~40 lines): counts, language mix, per-directory rollup with coupling and purpose, load-bearing/orchestrating symbols, entry points, parse errors. Read this before exploring an unfamiliar repo.

Task work-set: for a change (git rev) or a symbol, bundle the touched files' outlines plus call-graph packs for the most central touched symbols under one token budget. One call replaces affected + N outlines + N packs — and grepping a diff for touched names then reading each file whole to work it. Set type_impact=true when the target is a class/interface/struct/trait to also union in every type-usage site and implementor into the touched set — the full blast radius of changing a shared type's shape, not just its direct callers.