skills.rest
cwijayasundara
cwijayasundaraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

brownfield

Map existing codebases with dependency graphs and Markdown documentation.

3|Updated Jun 10, 2026
Search Tags:#risk assessment#code discovery#code mapping#brownfield analysis#change planning
One-click install
npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill brownfield-cwijayasundara
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brownfield
Source: https://github.com/cwijayasundara/claude_harness_eng_v5/tree/main/.claude/skills/brownfield
Command: npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill brownfield-cwijayasundara

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The brownfield Skill addresses the challenge of planning and modifying existing codebases without disrupting functionality or introducing new bugs.

Core Features & Use Cases

  • Code Discovery: Analyze the structure, dependencies, and key components of a codebase.
  • Risk Identification: Identify potential risks and areas with high fan-in without tests, cycles, or other structural risks.
  • Change Strategy: Recommend steps for changes, including the use of /vibe, /change, /refactor, /spec, and /auto.
  • Domain Glossary: Generate and confirm a domain glossary to improve understanding and communication.

Quick Start

Begin the discovery process in an existing repository using the command '/brownfield'.

Frequently Asked Questions about brownfield

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

FAQPage Schema
How do I analyze existing codebase structure and dependencies before making changes?▼

To analyze existing codebase structure, you can use a brownfield analysis process that inventories components, builds a dependency graph, and maps architecture to facilitate safe codebase modifications.

What is the best way to identify structural risks in a legacy codebase?▼

Identifying structural risks in a legacy codebase involves mapping modularity and tests to detect areas with high fan-in, missing test coverage, or cyclic dependencies that could introduce bugs during changes.

How do I plan code changes without disrupting existing functionality?▼

Planning code changes without disrupting functionality requires mapping the architecture, reviewing modularity, and generating a risk assessment to recommend a step-by-step change strategy.

Can I use Python scripts to map codebase architecture and generate documentation?▼

Yes, you can use Python scripts to discover and map codebase architecture, generating Markdown documentation that includes a domain glossary, dependency graphs, and recommended change strategies.

When do I need a domain glossary for brownfield code analysis?▼

You need a domain glossary for brownfield code analysis when planning complex modifications, as it confirms terminology to improve team communication and understanding before executing change strategies.

What are the limitations of automated code discovery for change planning?▼

Automated code discovery focuses on inventorying code and mapping dependencies but requires human validation of the generated domain glossary and risk assessment to ensure accurate change planning.

Related Skills

Explore More Software Engineering Skills→
fritzprixfritzprix
8

system-setup

Install and verify MCP runtime dependencies across Windows, Linux, and macOS.

Community
Intermediate
psaccpsacc

openspec-sync-specs

Merge delta specification changes into main openspec spec files.

Community
Advanced
richardmbaileyrichardmbailey

rb-architecture-review

Analyze codebase structure to identify architectural risks and coupling issues.

Community
Intermediate
Destynova2Destynova2
5

cli-audit-tangle

Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.

Community
Advanced