What problem does it solve? Understanding an unfamiliar codebase—locating where a function is implemented, tracing its callers and callees, or finding code by meaning—normally requires cloning the repo and reading files manually. This Skill provides structured remote access to repository structure, AST-level node details, and semantic code search without local checkout. ## Core Features & Use Cases - Hierarchical Code Location: Drill down from repository overview to packages, files, and individual nodes (functions, types, variables), then inspect dependency, reference, inheritance, and implementation relationships. - Semantic Code Search: Query code with natural language questions (e.g., "where is the auth middleware") across one or more repositories. - Service & Infra Lookup: Retrieve HTTP/RPC service API details, RPC call information for a PSM, and usage guidance for ByteDance internal components like Hertz, Kitex, Redis, and MySQL. - Use Case: When asked "how does generic invocation work in Kitex", start with get_repos_detail on the repo, narrow to the relevant package and file, then use get_nodes_detail recursively to map the full call chain before answering. ## Quick Start Ask the agent to analyze how a specific feature is implemented in a repository, for example: use repotalk to trace the callers of Closer.Close in github.com/cloudwego/kitex.
