AgentSkillsCN

code-exploration

适用于用户询问内部代码、各仓库间的实现细节、模式，或需要了解某项功能是如何构建时使用。可通过“X是如何实现的”、“代码在哪里可以找到”、“查找某个功能的实现”、“哪些仓库包含了这段代码”、“谁编写了这段代码”，或关于内部系统架构的代码相关问题触发相关操作。

SKILL.md
--- frontmatter
name: code-exploration
description: Use when the user asks about internal code, implementations, patterns across repositories, or needs to understand how something is built. Triggers on "how is X implemented", "where is the code for", "find the implementation of", "what repos contain", "who wrote the code for", or code architecture questions about internal systems.

Cross-Repository Code Exploration via Glean

When users need to understand code across internal repositories—beyond the local codebase—use Glean's code search to explore the entire organization's code.

Tool Naming

See the glean-tools-guide skill for Glean MCP tool naming conventions. Tools follow the pattern mcp__glean_[server-name]__[tool] where the server name is dynamic.

When This Applies

Use Glean code search when users ask about:

  • •How something is implemented (in other repos)
  • •Where the code for a system/service lives
  • •Who has been working on a codebase
  • •Similar implementations across the org
  • •Examples of how to use an internal API/library
  • •Code patterns used by other teams

Key Differentiator

Local tools (grep, glob) search only the current repo. Glean searches across ALL repositories in the organization. This is powerful for:

  • •Finding examples: "How do other teams handle authentication?"
  • •Understanding systems: "What repos touch the billing service?"
  • •Finding owners: "Who's been active in the payments codebase?"

Tool Selection

User IntentGlean Tool
Find code by content, pattern, or filecode_search
Find related design docs or specssearch
Identify code owners/contributorscode_search + employee_search
Read full file contentread_document

Query Patterns

Glean's code search understands natural language. Use filters for precision:

code
# Search by content
code_search "authentication middleware"
code_search "rate limiting implementation"

# Search by contributor
code_search "owner:\"John Smith\" billing service"
code_search "from:me updated:past_week"

# Search by time
code_search "after:2024-01-01 payments API"

# Search by file pattern
code_search "*.proto user service"

Workflow: Exploring a System

  1. •Find the code: code_search "[system name]"
  2. •Find the docs: search "[system name] design doc OR architecture"
  3. •Find the people: code_search "owner:* [system] updated:past_month"
  4. •Read details: read_document with URLs from results

Combining with Local Codebase

For comprehensive exploration:

  1. •Use Glean code_search to find related implementations across the org
  2. •Use local Grep and Glob to examine the current repository
  3. •Synthesize patterns and differences

Relationship to Commands

For structured workflows, suggest the relevant slash command:

  • •/glean-code:codebase-context [system] - Get comprehensive context
  • •/glean-code:find-examples [API/pattern] - Find usage examples
  • •/glean-code:code-owners [component] - Identify maintainers
  • •/glean-code:similar-code [pattern] - Find similar implementations