comprehensive-codebase-map

Coordinate four parallel agents to generate seven cross-referenced codebase documents.

9|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/calcosmic/Aether --skill comprehensive-codebase-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comprehensive-codebase-map
Source: https://github.com/calcosmic/Aether/tree/main/.aether/skills-codex/colony/comprehensive-codebase-map
Command: npx skills add https://github.com/calcosmic/Aether --skill comprehensive-codebase-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate four parallel analysis agents to deliver a complete, cross-cutting map of a complex codebase, consolidating architecture, data flows, API surfaces, conventions, debt, and risks into a unified document set.

Core Features & Use Cases

  • Parallel specialists generate ARCHITECTURE.md, DATA-FLOWS.md, API-SURFACES.md, INTEGRATIONS.md, CONVENTIONS.md, TECH-DEBT.md, and RISK-MAP.md to produce a holistic codebase view.
  • Documents are cross-referenced and organized to reveal dependencies, interfaces, and risk hotspots, supporting onboarding, planning, and governance.
  • Use cases include onboarding new engineers, scoping major refactors, and validating understanding after significant changes.

Quick Start

Launch all four agents in parallel to generate the seven documents and place them under .aether/data/codebase/; review and synthesize findings.

Frequently Asked Questions about comprehensive-codebase-map

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

FAQPage Schema
How do I generate a complete codebase map for large scale architecture onboarding?

To generate a codebase map, coordinate four parallel agents to produce structured documents covering architecture, data flows, API surfaces, and risks. These cross-referenced outputs provide a holistic view for onboarding and governance.

What is the best way to document API surfaces and data flows for a complex codebase?

The best way to document API surfaces and data flows is by running parallel analysis agents that generate structured, cross-referenced files. This approach reveals dependencies and interfaces across the entire codebase.

Can I use a multi-agent workflow to assess technical debt and risk hotspots during refactoring?

You can use a multi-agent workflow to assess technical debt and risk by generating dedicated documents like TECH-DEBT.md and RISK-MAP.md. These files identify hotspots to support planning and scoping major refactors.

How do I structure codebase documentation to reveal hidden integrations and conventions?

Structure codebase documentation by creating specialized files for integrations and conventions alongside architecture maps. Cross-referencing these documents reveals dependencies, shared interfaces, and established coding standards.

Does incremental codebase mapping work for validating understanding after significant code changes?

Incremental codebase mapping works for validating understanding by updating the existing structured documents after significant changes. This ensures the architecture, data flows, and risk maps remain accurate.

When do I need a full codebase map instead of a standard documentation generator?

You need a full codebase map when dealing with large, complex codebases requiring holistic views of architecture, data flows, and risk hotspots for onboarding or governance, rather than simple API documentation.