repository-analysis

Analyzes unfamiliar codebases and produces structured first-look architecture reports.

3|Updated Apr 8, 2025
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill repository-analysis-zanzythebar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repository-analysis
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/repository-analysis
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill repository-analysis-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you encounter an unfamiliar repository, it is hard to quickly understand its purpose, architecture, and key logic without reading every file. This Skill guides a systematic investigation and produces a grounded first-look report. ## Core Features & Use Cases - Structured Investigation Workflow: Follows a six-step process from establishing project purpose to tracing data flows and recording uncertainty as UNKNOWN with the smallest check to resolve it. - Tailored Report Sections: Covers overview, architecture, code structure, key components, algorithms, testing strategy, documentation quality, and risks, using only sections the repository supports. - Evidence-Based Claims: Cites paths and symbols, uses Mermaid diagrams when they clarify boundaries, and avoids inferring behavior from filenames alone. - Use Case: You clone an open-source project you have never seen and ask for an architecture overview; the Skill inspects entry points, traces flows, and returns a compact report with cited evidence. ## Quick Start Ask the assistant to analyze this repository and produce a first-look report covering its architecture, key components, and risks.

Frequently Asked Questions about repository-analysis

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

FAQPage Schema
How do I get an overview of an unfamiliar codebase?

Start by establishing the project purpose and entry points, then inspect the directory structure to identify application boundaries. Trace key flows from inputs to outputs and read representative source files before making correctness claims.

What should a repository analysis report include?

A useful report covers overview and use case, architecture and component interactions, code structure, key dependencies, important algorithms or data flows, testing strategy, documentation quality, and risks. Include only sections the repository actually supports.

Can codebase analysis work without reading every file?

Yes, a first-look analysis reads representative source files and tests rather than the entire tree. It records unresolved questions as UNKNOWN and names the smallest check that would resolve each uncertainty.

What are the limitations of automated repository analysis?

Analysis should not infer behavior from filenames alone or index home directories, vendor trees, and build outputs. Conclusions must be grounded in inspected files with cited paths and symbols as evidence.

When should I use a Mermaid diagram in a codebase report?

Use a Mermaid diagram only when it materially clarifies component boundaries or data flow. Keep it readable and high contrast, and omit it when prose and cited paths communicate the structure adequately.