explore

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Bounded, read-only codebase exploration. Do not write files or propose implementation — return triaged, structured findings for downstream skills.

限定范围的只读代码库探索。请勿编写文件或提议实现方案——请返回经过分类整理的结构化调研结果，供后续技能使用。

Workflow

工作流

Frame — state a concrete exploration question or hypothesis before searching.
Bounded discovery — find relevant modules, symbols, and entry points. MUST complete within 3 refinement cycles (search → read → refine). If unanswered after 3 cycles, return best partial results with explicit
```
risks_or_unknowns
```
.
Context triage — label findings:
```
core
```
(must include),
```
related
```
(include if space),
```
peripheral
```
(mention only if risk signal). Drop peripheral from handoff by default.
Map flow — trace control flow, data flow, and cross-file dependencies.
Extract surface — identify files to modify and expected side effects.
Handoff — return concise structured output (see below).

Discover project-specific terminology and naming conventions in cycle 1. Use discovered terms in subsequent searches instead of generic names.

明确范围 —— 在搜索前先提出具体的探索问题或假设。
限定范围调研 —— 查找相关模块、符号和入口点。必须在3轮优化周期内完成（搜索 → 阅读 → 优化）。如果3轮后仍未得到答案，请返回当前最优的部分结果，并明确标注
```
risks_or_unknowns
```
。
上下文分类 —— 为调研结果打标签：
```
core
```
（必须包含）、
```
related
```
（空间充足时包含）、
```
peripheral
```
（仅当存在风险信号时提及）。默认移交时丢弃边缘内容。
流程映射 —— 追踪控制流、数据流和跨文件依赖。
提取表层信息 —— 识别需要修改的文件以及预期的副作用。
结果移交 —— 返回简洁的结构化输出（见下文）。

在第1轮周期中发现项目专属的术语和命名规范。在后续搜索中使用发现的术语而非通用名称。

Output Format

输出格式

```
key_findings
```
— confirmed observations with file paths
```
files_to_touch
```
— with triage priority per file (core / related / peripheral)
```
risks_or_unknowns
```
— explicit gaps and unexplored areas
```
terminology_discovered
```
— non-obvious project naming (omit when not applicable)

```
key_findings
```
—— 附带文件路径的已确认观察结果
```
files_to_touch
```
—— 附带每个文件的分类优先级（核心/相关/边缘）
```
risks_or_unknowns
```
—— 明确的缺口和未探索区域
```
terminology_discovered
```
—— 非显而易见的项目命名（不适用时可省略）

External Dependencies

外部依赖

When exploring external libraries or APIs, use this source reliability hierarchy: official docs > versioned examples > changelog > blog posts > community forums > Stack Overflow.

Never mix guidance from different major versions
Check maintenance status before recommending a library
Capture version and context assumptions for every recommendation

探索外部库或API时，请遵循以下来源可靠性层级：官方文档 > 版本匹配的示例 > 变更日志 > 博客文章 > 社区论坛 > Stack Overflow。

切勿混合来自不同主版本的指引
推荐库之前先检查维护状态
为每个建议记录版本和上下文假设

Anti-Patterns

反模式

Speculating about behavior without repository evidence
Returning file lists without explaining each file's role in the flow
Assuming behavior from file names alone without verifying call sites
Proposing code edits or implementation during exploration
Overloading output with low-value file dumps instead of triaged signal

没有仓库证据就对行为进行推测
返回文件列表但不解释每个文件在流程中的作用
仅通过文件名假设行为，未验证调用点
探索过程中提议代码编辑或实现方案
输出塞满低价值的文件转储，而非经过分类的有效信号