archlet

Generate interactive architecture maps and PR diff overlays from import graphs.

43|5|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/superdesigndev/archlet --skill archlet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archlet
Source: https://github.com/superdesigndev/archlet/tree/main
Command: npx skills add https://github.com/superdesigndev/archlet --skill archlet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @colbymchenry/codegraph, madge, d3.

What problem does it solve?

This Skill solves the problem of architectural drift by automatically generating an interactive, provenance-backed map of your codebase, ensuring your documentation stays in sync with your actual implementation.

Core Features & Use Cases

  • Automated Mapping: Scans your repository to build a hierarchical, drill-down architecture map that visualizes modules and their dependencies.
  • PR Diff Overlays: Overlays specific PRs, commits, or branch changes onto the map to highlight exactly which architectural components are affected by a change.
  • Use Case: When onboarding a new engineer or planning a refactor, use this Skill to visualize the current dependency graph and verify the impact of proposed changes before merging.

Quick Start

Follow the instructions in the archlet SKILL.md file to build a map for this project.

Frequently Asked Questions about archlet

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

FAQPage Schema
How do I visualize codebase architecture and module dependencies?

You can visualize codebase architecture by scanning your repository to build an interactive, hierarchical dependency graph map that highlights module relationships and import structures.

How do I map the architectural impact of a pull request before merging?

Map pull request impact by overlaying specific commits or branch diffs onto an architecture map to highlight exactly which dependency graph components are affected by the changes.

What is architectural drift and how do I prevent it in software repositories?

Architectural drift occurs when implementation decouples from design. Prevent it by generating provenance-backed architecture maps that analyze import graphs to keep documentation synchronized with actual code.

Does this codebase visualization tool require madge and codegraph to extract dependency data?

Yes, generating interactive architecture maps requires integration with codegraph and madge to extract import graph data and d3 to render the visual module relationships.

How do I generate documentation for a software refactoring plan?

Generate refactoring documentation by analyzing call stacks and import graphs to produce a drill-down architecture map, verifying the structural impact of proposed changes on existing modules.

What are the limitations of using import graphs for code analysis?

Import graph code analysis relies on static dependency extraction, meaning it maps module relationships and call stacks effectively but may not capture dynamic runtime architecture changes.