brownfield-codebase-analysis

Analyze existing codebases to produce architecture, data flow, and tech debt reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a colony lands on an existing codebase (brownfield project), it needs structured understanding before it can plan work. This skill performs deep analysis producing a colonization report -- the colony's orientation map.

Core Features & Use Cases

  • Reconnaissance Sweep: scan top-level project structure to identify language, framework, build system, and entry points.
  • Architecture Mapping & API Catalog: trace dependencies and map module boundaries, identify data flow, and catalog public interfaces and integrations.
  • Data-layer and Tech-Debt insights: document storage patterns, migrations, and identify hotspots for improvement.

Quick Start

Provide a colonization report for the target repository summarizing language, architecture, data flows, and external integrations.

Frequently Asked Questions about brownfield-codebase-analysis

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

FAQPage Schema
How do I analyze an existing codebase to create an onboarding map?

Analyze an existing codebase by performing a reconnaissance sweep to identify the tech stack, map module boundaries, trace data flow, and catalog public APIs to produce a structured orientation dossier for new developers.

What is a brownfield codebase analysis and when do I need it?

A brownfield codebase analysis scans an existing project's code, tests, and deployments to map architecture and identify tech debt, needed when a team colonizes a project and requires structured understanding before planning work.

How do I map architecture and catalog APIs in a brownfield project?

Map architecture and catalog APIs by tracing dependencies, identifying data flow, and documenting public interfaces and external integrations, resulting in a structured colonization report detailing module boundaries.

Can this analysis identify tech debt and data layer patterns in an existing repository?

Yes, the analysis identifies tech debt hotspots and documents storage patterns and migrations within the data layer, producing actionable insights for improvement within the colonization dossier.

What's the best way to orient a team colonizing an existing project?

The best way to orient a colonizing team is to generate a colonization-ready orientation map covering the tech stack, architecture, API catalog, data layer, and onboarding guidance for the target repository.

Do I need to provide specific files to get a colonization report for my repository?

You need to provide access to the target repository containing code, tests, and deployments so the analysis can scan the project structure and summarize language, architecture, data flows, and external integrations.