architecture

Dependency blast radius is calculated by analyzing module topology, tracing impacted callers, classifying modules as safe or at-risk, and validating against bounded contexts. This Skill automates that computation and produces a structured architecture risk report for GitHub PR review.

Circular dependencies and God Object risks are detected by generating dependency graphs and deriving actionable structural signals from module coupling. This Skill analyzes dependency topology to identify these architectural anti-patterns and escalates findings when refactoring is required.

Bounded context boundaries are enforced by validating dependency topology against layer constraints defined in CONTEXT.md. When a proposed change violates these boundaries, the Skill blocks progress and publishes a structured blast-radius report as a GitHub PR comment.

Preventing structural drift requires computing a dependency blast radius before a change is committed, then blocking progress when topology violates defined boundaries. This Skill maps module coupling, classifies deep vs shallow modules, and cross-references open architecture issues to avoid duplicate work.

Module coupling can be mapped and modules classified as deep or shallow by generating dependency outputs to the filesystem and deriving structural metrics. This Skill automates that topology analysis, summarizing metrics into context and producing architecture risk reports.

A CONTEXT.md file is required to define layer constraints and bounded contexts that the Skill validates dependency topology against. Without it, boundary enforcement and fragility escalation cannot be applied to the computed blast radius during PR review.