Agent Skills › repowise-dev/repowise › codebase-exploration

codebase-exploration

GitHub

用于通过 Repowise MCP 工具探索和理解代码库，提供架构概览、符号搜索及智能问答，辅助开发者快速定位代码与模块。

plugins/codex/skills/codebase-exploration/SKILL.md repowise-dev/repowise

Trigger Scenarios

需要了解代码库整体架构或模块分布询问特定功能或符号的实现位置与逻辑在编写代码前查找相关文件和上下文

Install

npx skills add repowise-dev/repowise --skill codebase-exploration -g -y

More Options

Non-standard path

npx skills add https://github.com/repowise-dev/repowise/tree/main/plugins/codex/skills/codebase-exploration -g -y

Use without installing

npx skills use repowise-dev/repowise@codebase-exploration

指定 Agent (Claude Code)

npx skills add repowise-dev/repowise --skill codebase-exploration -a claude-code -g -y

安装 repo 全部 skill

npx skills add repowise-dev/repowise --all -g -y

预览 repo 内 skill

npx skills add repowise-dev/repowise --list

SKILL.md

Frontmatter

{
    "name": "codebase-exploration",
    "description": "Use when exploring, understanding, or answering questions about a Repowise-indexed codebase, including architecture, where code is implemented, how a module works, or which files are relevant before reading source."
}

Codebase Exploration with Repowise

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.

Which tool for which question

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 + one `confidence` trust signal. Collapses the search → read → reason loop.
Find a symbol, file, or fuzzy concept	`search_codebase(query="…")` — hybrid search. `mode="auto"` routes an identifier to indexed symbol hits (`symbol_id`/line bounds → pipe into `get_symbol`), a path to file pages (→ `get_context`), and prose to semantic wiki search (each hit reports `search_method`: `embedding` vs `bm25`). Force a branch with `mode=symbol\|path\|concept\|hybrid`; narrow symbols with `symbol_kind`.
A triage card for specific files/symbols	`get_context(targets=[…])` — title, summary, signatures, hotspot bit, top callers, decision titles, symbol_ids (a row without one is `path::name`). 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`.

Recommended flow

New area you don't know → get_overview() once.
A specific question → get_answer(question=…) first.
- High confidence → answer it, cite the paths.
- medium/low confidence → follow best_guesses[0].file or fallback_targets[0] into get_context, then get_symbol for bytes.
A named symbol or a path → search_codebase(query="Name") / search_codebase(query="path/to/file.py"); symbol hits pipe straight into get_symbol, file hits into get_context.
More files around a concept → search_codebase, then get_context on the hits (batched), then get_symbol only for the bodies you actually need.

Fall back to your own file-reading and searching tools only when the indexed context doesn't cover the specific detail the user asked about.

Trust signals — verify when

_meta.stale_warning is present (the index has diverged from HEAD), or
confidence is medium/low, or
a result's search_method is bm25.

Otherwise the response is current — act on it.

Error handling

"No repositories found. Run 'repowise init' first." → suggest /prompts:repowise-init. Add --no-editor-setup if this repo is a scratch clone, a fixture, or a worktree: init otherwise repoints the user's single global repowise MCP entry at it.
MCP tools unavailable → prefer the matching CLI slash commands when the plugin is installed (/prompts:repowise-ask, /prompts:repowise-context, /prompts:repowise-symbol, /prompts:repowise-search) rather than grepping blind.
get_answer/search_codebase come back empty → the repo may have a template-rendered wiki. Fall back to get_context with explicit paths, and note that model-written pages (repowise generate, or /prompts:repowise-init with an LLM provider) unlock richer docs + semantic search.
Tools fail to connect at all → the repowise binary may not be installed; suggest /prompts:repowise-init.

Version History

09471b8 Current 2026-10-19 07:01
优化了 get_answer 的信任信号机制，将检索质量与置信度合并为单一的 confidence 指标，并改进了答案覆盖度评分逻辑及缓存版本。
8f69324 2026-09-22 12:17
修正失败保护机制中的提示文案，将具体的工具名称（如 Read/Grep）改为通用的能力描述，以适配不同 MCP 客户端。
370793f 2026-08-19 23:15
重构插件内容生成逻辑，将Codex和Claude Code的技能源合并为共享单点，消除文档漂移并统一渲染。
b5f4753 2026-07-25 05:12