← ClaudeAtlas

ccg-namespacelisted

Isolate CCG graph build, search, documentation discovery, and analysis by namespace. Use when working across multiple repositories or services, preventing cross-project graph leakage, choosing safe scoped-update semantics, federating supported reads, or traversing materialized cross-namespace references. Do not use for ordinary single-repository work that fits the default namespace.
tae2089/code-context-graph · ★ 18 · AI & Automation · score 79
Install: claude install-skill tae2089/code-context-graph
# ccg-namespace — Graph Namespace Isolation Use namespaces to isolate graph rows for different services or repositories. CCG no longer manages uploaded namespace files; callers provide a filesystem path to `build_or_update_graph` or use CLI build/update commands with `--namespace`. ## Core Pattern ```bash ccg build ./services/payment --namespace payment ccg build ./services/users --namespace users ccg search --namespace payment "checkout" ccg status --namespace users ``` Through MCP: ```text build_or_update_graph(path: "/repos/payment", namespace: "payment", full_rebuild: true) list_namespaces() search(namespace: "payment", query: "checkout") search(namespace: "payment", query: "why does checkout retry a failed capture") ``` `list_namespaces` reports every namespace holding graph data with its node count — the first call before interpreting any namespace-scoped result. Both `search` query shapes work namespace-scoped: keywords and plain-language questions answered from recorded reasons. ## Scoped Update Decision Classify a partial incremental update as either an authoritative snapshot or a maintenance work slice. Use the `ccg` skill's Scoped Update Safety for the exact `include_paths` and replacement arguments, then record which behavior was chosen for the namespace. ## Operational Guidance - Use one namespace per service or repository when graph state must remain isolated. - Use the default namespace for ordinary single-repository local work. - Pass the same namesp