repo-visualizer

Generate interactive architecture visualization diagrams from repository structure and dependencies.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/perfectuser21/cecelia --skill repo-visualizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-visualizer
Source: https://github.com/perfectuser21/cecelia/tree/main/packages/workflows/skills/repo-visualizer
Command: npx skills add https://github.com/perfectuser21/cecelia --skill repo-visualizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of interactive architecture visualization diagrams for any code repository, helping to understand complex codebases and identify structural issues.

Core Features & Use Cases

  • Automated Architecture Mapping: Generates visual diagrams based on repository structure, file dependencies, and code analysis.
  • Problem Identification: Highlights issues like large files, duplicated modules, and dependency problems.
  • Use Case: Quickly understand the architecture of a new project, identify code smells, and visualize the flow of execution between different components, including LLM-integrated parts.

Quick Start

Use the repo-visualizer skill to generate an architecture map for the current repository.

Frequently Asked Questions about repo-visualizer

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

FAQPage Schema
How do I visualize code architecture for a complex repository?

To visualize code architecture, this Skill analyzes repository file structure and dependencies to generate interactive diagrams, classifying components by execution type and architectural layer.

Can I generate architecture diagrams for Node.js monorepos and microservices?

Yes, architecture visualization supports Node.js, React, monorepos, and microservices, mapping dependencies and visualizing execution flow between components.

What is the best way to map dependencies and identify code smells in a codebase?

Architecture visualization identifies structural code smells by detecting large files, dispersed modules, functional overlap, and dependency problems across the codebase.

Does this architecture mapping tool require external dependencies to run?

No external dependencies are required to generate architecture visualizations; the Skill operates independently to analyze repository characteristics and map component health status.

How does code visualization handle LLM-integrated components?

Code visualization handles LLM-integrated components by analyzing their characteristics and mapping the execution flow between them and other architectural layers.