codebase-analyzer

Generate a structured Chinese project research report with source paths and line numbers.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/RollRollRoll/agent-toolkit --skill codebase-analyzer-rollrollroll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-analyzer
Source: https://github.com/RollRollRoll/agent-toolkit/tree/main/resources/skills/codebase-analyzer
Command: npx skills add https://github.com/RollRollRoll/agent-toolkit --skill codebase-analyzer-rollrollroll

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineers who are new to a software project to quickly build a complete mental model by delivering a structured Chinese调研报告 that explains what the project does and how it is implemented. The report emphasizes source-backed conclusions and traceable paths to code.

Core Features & Use Cases

  • Structured discovery reports: provides project定位、核心功能、用户价值、架构与技术栈、关键实现路径、端到端流程示例等信息。
  • Multi-depth outputs: supports 快速概览、标准调研、深度报告; users choose depth.
  • Evidence-driven conclusions: every important conclusion includes a source path and line number to verify against code.

Quick Start

将 SKILL.md 与 references/ 复制到目标平台的 skill 目录即可直接使用。

Frequently Asked Questions about codebase-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a structured research report for an unfamiliar codebase?

To generate a structured codebase research report, this Skill extracts the project's purpose, architecture, tech stack, and end-to-end flows from the repository. It outputs a structured Chinese report with exact source paths and line numbers for rapid onboarding.

What is the best way to onboard quickly by analyzing a repository's architecture and data models?

Analyzing a repository's architecture and data models is best handled by generating a structured discovery report. This Skill extracts core features and implementation details, citing exact source paths to verify conclusions against code without guessing from names.

Can I use this codebase analysis tool to trace end-to-end flows with exact source paths?

Yes, you can use this codebase analysis tool to trace end-to-end flows. It provides evidence-driven conclusions where every important architectural finding includes a source path and line number to ensure traceable verification against the actual code.

Does the codebase research report support different depths of analysis like quick overviews?

Yes, the codebase research report supports multiple depth outputs. Users can choose between a quick overview, standard research, or a deep report to analyze external interfaces and implementation details according to their onboarding needs.

How do I set up the codebase analyzer to start researching project implementation details?

To set up the codebase analyzer, copy the SKILL.md file and the references directory into the target platform's skill directory. Once installed, it is ready to directly extract implementation details and generate the research report.

Why do I need exact source paths and line numbers in a project onboarding report?

You need exact source paths and line numbers in a project onboarding report to ensure evidence-driven conclusions. This prevents guessing from file names and allows you to directly verify the extracted architecture and data models against the actual source code.