codebase-exploration
Use Repowise-indexed codebase exploration tools to answer questions about a repository's architecture, module functionality, file locations, and code connections before reading raw source files. Call `get_overview()` for initial context, `search_codebase()` to find relevant files and modules, and `get_dependency_path()` to understand how different areas connect, reserving direct source inspection only when indexed information is insufficient.
git clone --depth 1 https://github.com/repowise-dev/repowise /tmp/codebase-exploration && cp -r /tmp/codebase-exploration/plugins/codex/skills/codebase-exploration ~/.claude/skills/codebase-explorationSKILL.md
# Codebase Exploration With Repowise This project has a Repowise intelligence layer. Use Repowise MCP tools before broad source browsing so the answer starts from indexed docs, ownership, graph structure, git signals, and decisions. ## Starting A New Exploration Task Call `get_overview()` first. It returns the architecture summary, module map, entry points, and tech stack. ## Answering How Or Where Questions 1. Call `search_codebase(query="topic or symbol")` to find relevant documented modules and files. 2. Call `get_context(targets=[...])` with all relevant files from the search results in one batch. 3. Read raw source only after the indexed context is not specific enough for the user’s question. ## Understanding Connections Between Modules Call `get_dependency_path(source="module_a", target="module_b")` when the user asks how two areas connect. ## Getting Diagrams Call `get_architecture_diagram(scope="module", path="path/to/module")` for a subsystem diagram, or `get_architecture_diagram()` for the full repository. ## Error Handling - If tools report that no repositories were found, suggest running `repowise init`. - If `search_codebase` has no useful results, the repository may be index-only; fall back to `get_context` with specific paths. - If MCP tools are unavailable, proceed with normal source inspection and mention that Repowise context was unavailable.
Use when a task asks why code is built a certain way, proposes architectural changes, compares implementation approaches, or mentions decision markers such as WHY, DECISION, TRADEOFF, or ADR in a Repowise-indexed repository.
>
>
Use when the user asks about unused code, cleanup, deleting files or exports, refactoring old areas, reducing bundle size, code hygiene, technical debt, or maintenance in a Repowise-indexed repository.
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.