skills.rest
ztdevelops
ztdevelopsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

codebase-analyzer

Analyze codebases to trace functions and data flow with file:line references.

1|Updated Jan 23, 2026
Search Tags:#architecture#documentation#codebase#analysis#tracing#data-flow#file-line
One-click install
npx skills add https://github.com/ztdevelops/claude-code-skills --skill codebase-analyzer-ztdevelops
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-analyzer
Source: https://github.com/ztdevelops/claude-code-skills/tree/main/public/codebase-analyzer
Command: npx skills add https://github.com/ztdevelops/claude-code-skills --skill codebase-analyzer-ztdevelops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The codebase-analyzer skill helps developers and reviewers quickly understand how an existing codebase is implemented by producing precise, file-and-line referenced explanations of program flow and component interactions.

Core Features & Use Cases

  • Implementation Tracing: Read source files, identify key functions and follow call paths to explain how logic flows across files.
  • Data Flow Mapping: Trace data from entry points to exit points and document transformations and state changes with exact file:line citations.
  • Architectural Documentation: Produce ASCII architecture and flow diagrams, list entry points, configuration points, and describe integration surfaces for onboarding or handoff.
  • Use Case: Use when you need a clear, evidence-backed description of how a feature is implemented for onboarding, audits, or documentation updates.

Quick Start

Ask the codebase-analyzer to trace the data flow for a specific feature by naming the entry file and target function and write the complete analysis to ANALYSIS.md with file:line references.

Frequently Asked Questions about codebase-analyzer

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

FAQPage Schema
How do I trace data flow across modules in a large codebase?▼

You can trace data flow across modules by reading source files, tracking data from entry points to exit points, and documenting transformations with exact file:line citations in an ANALYSIS.md report.

What is the best way to document component interactions for codebase onboarding?▼

The best way to document component interactions for onboarding is by producing an ANALYSIS.md report containing ASCII architecture diagrams, entry points, configuration points, and integration surfaces with file-level precision.

Can I map function call paths and reference exact file lines in a medium repository?▼

Yes, you can map function call paths in medium-to-large repositories by identifying key functions and following call paths across files to produce precise file:line referenced explanations of program flow.

Do I need read access to all repository files to generate architecture diagrams?▼

Generating architecture diagrams requires read access to repository files and the ability to reference exact file paths and line numbers while producing ASCII diagrams for the analysis report.

Why use file-level precision when tracing implementation logic for audits?▼

Using file-level precision when tracing implementation logic provides evidence-backed descriptions of how features are implemented, citing exact file paths and line numbers to support codebase audits and handoffs.

Related Skills

Explore More Software Engineering Skills→
korchasakorchasa
3

flow-answer

Analyze documentation and source code to answer user questions in Autonomous Mode.

Community
Advanced
galz10galz10
454

code-researcher

Document codebase architecture and data flows with file:line references.

Community
Basic
The13thNodeThe13thNode
3

document-release

Scan git diffs and update markdown documentation for releases.

Community
Intermediate
adrielpadrielp
20

codebase-analyzer

Trace data flow and explain code with file:line references.

Community
Advanced