code-kglisted

Builds and queries a SQLite+FTS5 knowledge graph over any codebase - import/dependency edges, symbols with line ranges, entry points, liveness tiers that shortlist dead code, agent-tooling layer, data-store inventory. Parses python, javascript/typescript, go, rust, c/c++, java, c#, powershell, bash, sql, terraform, docker/compose/CI yaml, make, html/css, json, toml and markdown, stdlib only; understands tsconfig aliases and Django/Next.js wiring. Use to index, map or query a repo ("what imports X", "blast radius", "find dead code", "what databases does this use"), orient in an unfamiliar repo, trace how two files connect, or fold test coverage in to find never-executed code. Markdown corpora go to obsidian-kg. Fully offline except `coverage run` and `data --inspect`, both consent-gated.
anton-winter-arch/dotagents · ★ 1 · Data & Documents · score 72

Install: claude install-skill anton-winter-arch/dotagents

# code-kg X-ray a codebase once, then answer from the graph instead of grepping. One stdlib engine: EXECUTE `scripts/code_kg.py` via Bash for every operation - never reimplement its parsing inline. Storage is `<repo>/.code-kg/` (config.json + a rebuildable, gitignored db). Every read command re-ingests on drift, so answers track the live tree without you managing freshness. Languages parsed: python (AST-exact), javascript/typescript, bash, go, rust, c/c++, java, c#/msbuild, powershell, sql, terraform, dockerfile, compose, github actions, make, html, css, json, toml, markdown. ## Commands Run each row below as `python3 <skill-dir>/scripts/code_kg.py <row>`. The repo path is always the first argument after the command name. `--json` is optional on every command, accepted at any position after the command name (conventionally last): default output is rendered text, `--json` makes it machine-readable. | Command | Gives you | |---|---| | `init <repo>` | scaffold `.code-kg/` + first ingest (once per repo) | | `ingest <repo>` | full rebuild (rarely needed - reads auto-refresh) | | `search <repo> "question"` | ranked hits, symbols first, each with `file:start-end` | | `query <repo> 'fts5 AND terms'` | raw FTS5 over file text | | `read <repo> <target>` | whole unit: `path`, `path:A-B`, or `path::Qual.name` | | `file <repo> <path>` | one file: role, symbols, edge counts, entry points | | `symbols <repo> <path-or-name>` | outline of a file, or find a symbol by name | | `imports <re