analyze-architecture

Analyzes backend/web application architecture and generates a structured health report.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Fohlio/ai-tools --skill analyze-architecture-fohlio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-architecture
Source: https://github.com/Fohlio/ai-tools/tree/main/skills/analyze-architecture
Command: npx skills add https://github.com/Fohlio/ai-tools --skill analyze-architecture-fohlio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding to an unfamiliar codebase requires a rapid, thorough view of the system's architecture, boundaries, and health. This skill automates a structured review to identify context, domains, components, data models, integrations, quality attributes, security, observability, and evolution risks.

Core Features & Use Cases

  • System Context & Boundaries assessment: identifies external consumers/dependencies and boundary clarity.
  • Domains & Bounded Contexts: highlights core domain, explicit boundaries, and cross-domain coupling.
  • Components & Service Map: outlines high-level structure, responsible modules, and entry points; exposes potential god components.
  • Architecture Quality & Evolution: evaluates modularity, coupling, cohesion, and how new features can be added without destabilizing the codebase.
  • Practical use cases include onboarding to a new project, pre-mortem risk discovery, and architecture health checks before major refactors or migrations.

Quick Start

Run the architecture assessment against your repository to generate a structured health report.

Frequently Asked Questions about analyze-architecture

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

FAQPage Schema
How do I perform an architecture health check on a codebase?

An architecture health check evaluates context, domains, components, quality attributes, data models, and observability against a structured checklist to assess codebase health and evolution risk. It generates a structured report with actionable recommendations.

What is the best way to assess bounded contexts and domain coupling before a refactor?

Assess bounded contexts by highlighting the core domain, explicit boundaries, and cross-domain coupling within the codebase. This structured evaluation exposes potential god components and identifies evolution risks during major migrations or refactors.

Can I evaluate system observability and security during a codebase onboarding process?

Yes, you can evaluate system observability and security during codebase onboarding. The assessment collects evidence from source files to document integrations, quality attributes, and boundary clarity, ensuring comprehensive onboarding readiness.

How does component analysis identify god components and high-level service structure?

Component analysis outlines the high-level structure, responsible modules, and entry points within the codebase. It systematically exposes potential god components by evaluating modularity, coupling, and cohesion across the system's service map.

When do I need a structured architecture review for my backend application?

A structured architecture review is needed before major refactors, during migrations, or when onboarding to an unfamiliar codebase. It automates evidence collection from source files to identify context, boundaries, and evolution risks.

Does architecture risk assessment work for small web application codebases?

Yes, architecture risk assessment applies to backend and web application codebases of varying sizes. It evaluates onboarding readiness and health by systematically checking domains, components, and quality attributes against a structured checklist.