Help us improve
Share bugs, ideas, or general feedback.
From repowise
Explores codebases with Repowise indexing for architecture understanding, searching, and answering questions without raw source grepping.
npx claudepluginhub repowise-dev/repowise --plugin repowiseHow this skill is triggered — by the user, by Claude, or both
Slash command
/repowise:codebase-explorationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This project has a Repowise intelligence layer. Before grepping and reading raw
Answers codebase questions by tracing flows and researching topics. Two modes: autonomous (structured output for subagents) and interactive (narrative with checkpoints).
Answers repository questions grounded entirely in source code evidence. Use for codebase queries, understanding specific files/functions/components, or 'how X works'/'where Y defined'.
Enables semantic search, grep, artifact fetching, call graph tracing, and Q&A across CodeAlive-indexed codebases, repos, docs, and dependencies.
Share bugs, ideas, or general feedback.
This project has a Repowise intelligence layer. Before grepping and reading raw source to understand the codebase, reach for the Repowise MCP tools — they return documentation, ownership, history, decisions, and graph structure that plain file reads don't, usually in one round-trip instead of many.
| You want… | Call |
|---|---|
| First orientation in an unfamiliar repo | get_overview() — architecture summary, key modules, entry points, git health, knowledge map. Skip it once you have the map. |
| A direct answer to "how/where/why does X work" | get_answer(question="…") — synthesised answer with citations + a retrieval_quality signal. Collapses the search → read → reason loop. |
| Candidate files for a fuzzy concept | search_codebase(query="…") — semantic wiki search. Each hit reports search_method (embedding vs bm25 fallback). Use Grep for exact identifiers. |
| A triage card for specific files/symbols | get_context(targets=[…]) — title, summary, signatures, hotspot bit, top callers, decision titles, symbol_ids. Batch many targets in one call. |
| The actual source of one symbol | get_symbol("path/to/file.py::Name") — exact bytes with line bounds. Cheaper than Read + offset math. Use a symbol_id from get_context. |
get_overview() once.get_answer(question=…) first.
medium/low confidence → follow best_guesses[0].file or
fallback_targets[0] into get_context, then get_symbol for bytes.search_codebase, then get_context on the
hits (batched), then get_symbol only for the bodies you actually need.Fall back to raw Read/Grep only when the indexed context doesn't cover the specific detail the user asked about.
_meta.stale_warning is present (the index has diverged from HEAD), orretrieval_quality is partial/weak, orsearch_method is bm25.Otherwise the response is current — act on it.
/repowise:init.get_answer/search_codebase come back empty → the repo may be in index-only
mode (no wiki). Fall back to get_context with explicit paths, and note that
full mode (/repowise:init with an LLM provider) unlocks docs + semantic search.repowise binary may not be installed;
suggest /repowise:init.