analyzing-architecture

Analyzes Java and .NET codebases to generate architecture and migration research artifacts.

35|8|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/microsoft/github-copilot-modernization --skill analyzing-architecture-microsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyzing-architecture
Source: https://github.com/microsoft/github-copilot-modernization/tree/main/plugins/github-copilot-modernization/skills/analyzing-architecture
Command: npx skills add https://github.com/microsoft/github-copilot-modernization --skill analyzing-architecture-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes a codebase to reveal architecture patterns, tech choices, data models, integration points, and migration risks to inform planning and implementation.

Core Features & Use Cases

  • Architecture Discovery: identify modules, boundaries, dependencies, and layering.
  • Data Models & Tech Stack Inventory: enumerate entities, schemas, frameworks, and runtime considerations.
  • Research Artifacts: generate artifacts such as project-structure.md, tech-stack.md, data-model.md, architecture-summary.md, migration-risks.md, infrastructure.md, test-coverage.md, deployment.md for downstream planning.

Quick Start

Analyze your repository to generate the artifact set listed in the Output section.

Frequently Asked Questions about analyzing-architecture

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

FAQPage Schema
How do I analyze a codebase to identify architecture patterns and tech stack?▼

Analyzing a codebase for architecture patterns involves identifying modules, boundaries, dependencies, layering, frameworks, and runtime considerations. This skill processes Java and .NET projects with multi-module structures to reveal these architectural elements.

How do I discover data models and integration points in an unknown codebase?▼

Discovering data models and integration points involves enumerating entities, schemas, and external dependencies. This skill analyzes your repository to map these integration points and data structures, generating a dedicated data-model artifact for downstream planning.

Can I use this architecture analysis for Java and .NET projects with multiple deployment targets?▼

Yes, this architecture analysis supports Java and .NET projects with multi-module structures, unknown dependencies, and multiple deployment targets, generating artifacts like deployment.md and infrastructure.md to capture these specific deployment configurations.

What research artifacts do I need for planning a codebase migration?▼

Research artifacts needed for migration planning include project-structure.md, tech-stack.md, data-model.md, architecture-summary.md, migration-risks.md, infrastructure.md, test-coverage.md, and deployment.md, which document codebase architecture and identify potential migration risks.

What is the best way to assess migration risks in a multi-module codebase?▼

Assessing migration risks in a multi-module codebase requires analyzing unknown dependencies, architecture patterns, and integration points. This skill generates a migration-risks.md artifact that captures these risks to inform downstream planning and inventory tasks.

Why do I need to generate test-coverage and deployment artifacts during architecture discovery?▼

Generating test-coverage and deployment artifacts during architecture discovery captures runtime considerations and deployment configurations. These artifacts, alongside tech-stack and infrastructure documentation, provide downstream planning tasks with a complete architectural context.