← ClaudeAtlas

reposkein-graph-raglisted

Navigates the local RepoSkein Code Property Graph to understand repository architecture. Use whenever modifying code, tracing dependencies, assessing change impact, or summarizing functions in a repo containing .reposkein/.
reposkein/reposkein · ★ 14 · AI & Automation · score 73
Install: claude install-skill reposkein/reposkein
# RepoSkein Graph Navigation You are equipped with the RepoSkein MCP server. It exposes a deterministic graph of the repository — directories, files, classes, functions, imports, and calls — that you enrich with natural-language summaries just-in-time. Do NOT guess file dependencies, and do NOT explore the repo by directory listing or grep when the graph can answer structurally. The server resolves the target repo automatically from your working directory — no setup is required. If a tool call returns an error naming `list_repos`/`select_repo` or `REPOSKEIN_REPO_PATH`, do not abandon these tools and fall back to grep — the error is actionable: - **No repo found at all** — run `reposkein-mcp init` in the repo (if it has no `.reposkein/` yet), or set `REPOSKEIN_REPO_PATH`. - **Multiple repos found (workspace mode)** — the error names the candidates. Call `list_repos` to see them (path, name, node/edge counts), then `select_repo` with one candidate's `path` or `name` — this sets the active repo for the rest of the session, so you only do it once. Retry the call that failed. ## Tools - **`list_repos`** / **`select_repo`** — only needed in workspace mode (multiple sibling repos, no unambiguous default). `list_repos` enumerates what was discovered; `select_repo` (a `path` or `name` from that list) sets the active repo for every repo-scoped tool below, for the rest of the session. Skip these in the common single-repo case — resolution just works. - **`semanti