Forge-Architecture-Analysis

Interprets codebase knowledge graphs to map components, patterns, and structural risks.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-architecture-analysis-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Architecture-Analysis
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/02-Architecture/Forge-Architecture-Analysis
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-architecture-analysis-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding the architecture of an unfamiliar or legacy codebase is slow and error-prone when done by reading source files alone. This Skill turns the knowledge graph and analysis report produced by a codebase analysis tool into an engineering-grade architectural understanding, so teams can assess structure without manually tracing every dependency. ## Core Features & Use Cases - Component and Boundary Mapping: Identifies major components, modules, and their inter- and intra-component edges from graph nodes and communities. - Pattern and Risk Detection: Recognizes architectural patterns (layered, hexagonal, microservice, monolith, event-driven) and flags structural risks such as cyclic dependencies, god objects, hidden coupling, and boundary violations. - Confidence-Labelled Findings: Preserves EXTRACTED, INFERRED, and AMBIGUOUS confidence labels on every structural claim, and verifies graph freshness before treating structure as current. - Use Case: When onboarding an unfamiliar repository, feed the knowledge graph and GRAPH_REPORT.md into this Skill to produce an architectural summary, component map, and traceable structural risk findings as inputs to an Architecture Assessment. ## Quick Start Analyze the knowledge graph and analysis report for this repository and produce an architectural summary with a component map and structural risk findings for the Architecture Assessment.

Frequently Asked Questions about Forge-Architecture-Analysis

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

FAQPage Schema
How do I analyze the architecture of an existing codebase?▼

First generate a knowledge graph and analysis report using a codebase analysis tool, then apply this Skill to interpret them. It maps components and boundaries, identifies patterns, and produces confidence-labelled structural findings for an Architecture Assessment.

What is a knowledge graph in codebase analysis?▼

A knowledge graph represents code entities as nodes and their relationships as confidence-labelled edges (EXTRACTED, INFERRED, AMBIGUOUS). This Skill reads the graph and its report to identify components, god nodes, and surprising cross-cutting connections.

Does this Skill build the code graph itself?▼

No. Building the graph and running the analysis tool belong to the Tooling layer per ADR-008. This Skill only interprets the tool's outputs, so the underlying tool can be replaced without changing the Skill.

When should I not use architecture analysis on a codebase?▼

Do not use it when no knowledge graph or analysis report exists yet, when the question concerns a single function's behavior (use debugging instead), or when deciding what to build next (use solution architecture instead).

How are confidence labels used in architecture findings?▼

Every structural claim keeps its edge confidence: EXTRACTED findings are reported as fact, INFERRED as likely with stated basis, and AMBIGUOUS as unverified requiring human review. Stale graphs must be refreshed before analysis.