Repo Analysis

Overview

Use this skill to turn an unfamiliar repository into a concrete engineering assessment. The goal is not to restate the README, but to identify what the project is, how it is structured, how it runs, where the main boundaries are, and what risks or follow-up questions matter.

Default mindset:

• engineering-first
• evidence-first
• broad scan before deep reading
• explicit separation of fact, inference, and unknowns

Output modes

Choose one mode as early as possible. If the user does not specify, choose the lightest mode that still answers the request. Prefer explicit user choice over automatic detection.

Mode 1: 速读版

Use when the user wants a fast understanding. Typical asks:

• "读一下这个项目"
• "帮我看看这个 repo 是干嘛的"
• "快速理解一下这个仓库"

Goal:

• tell the user what the project is
• identify stack and repo shape
• map the top-level modules
• summarize major strengths and risks
• recommend what to read next

Depth:

• broad scan
• minimum high-signal files
• one or two entry points at most

Expected output size:

• short to medium

Mode 2: 架构版

Use when the user wants system structure, runtime flow, or design analysis. Typical asks:

• "给我一个架构分析"
• "这个项目主链路是什么"
• "帮我拆一下模块边界"
• "分析它怎么运行的"

Goal:

• explain the system shape
• map module boundaries and ownership
• trace one or two critical execution paths
• identify important abstractions and complexity hotspots

Depth:

• targeted deep reading of core services and entry points
• may include backend, frontend, plugin, runtime, queue, or deployment chain

Expected output size:

• medium to long

Mode 3: 接手评审版

Use when the user wants adoption, maintenance, or takeover judgment. Typical asks:

• "这个项目值不值得接手"
• "给我一个接手评审"
• "我们要不要基于它二开"
• "从工程上看风险大不大"

Goal:

• judge maturity, maintainability, and operational complexity
• identify high-risk modules and safer entry points
• estimate onboarding/takeover cost
• suggest a pragmatic reading and change strategy

Depth:

• architecture + repo health + risk evaluation
• optional GitHub enhancement when public metadata matters

Expected output size:

• medium to long

Automatic mode selection

When the user does not explicitly choose a mode, infer it from intent.

Default to 速读版

Use 速读版 when the user says things like:

• "读一下这个项目"
• "看看这个 repo"
• "这个项目怎么样"
• "快速理解一下"
• "帮我看看它是做什么的"

Behavior:

• give a concise engineering summary
• if it is a public GitHub repo, optionally add a light GitHub health layer
• do not expand into deep architecture unless needed
• by default, follow only one main execution path; avoid second-layer architecture decomposition unless the user asks

Default to 架构版

Use 架构版 when the user says things like:

• "给我一个架构分析"
• "主链路是什么"
• "模块边界怎么划分"
• "怎么运行的"
• "message flow / runtime / workflow 怎么走"