architecture-audit

Audit codebases against claimed architecture to identify drift and cohesion issues.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/radenadri/skills-alena --skill architecture-audit-radenadri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-audit
Source: https://github.com/radenadri/skills-alena/tree/main/skills/architecture-audit
Command: npx skills add https://github.com/radenadri/skills-alena --skill architecture-audit-radenadri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineers often struggle to understand whether a codebase aligns with its stated architecture, and to identify drift, coupling, and cohesion issues. This Skill guides a structured audit of structure, dependencies, and patterns to reveal architectural health.

Core Features & Use Cases

  • Phase 1: Structure Mapping
  • Phase 2: Dependency Analysis
  • Phase 3: Pattern Consistency
  • Phase 4: Cohesion and Boundaries
  • Phase 5: Cross-Cutting Concerns
  • Phase 6: Evolution Assessment
  • Use cases include evaluating refactors, migrations, onboarding, and governance.

Quick Start

Run an architecture audit on the target codebase to map structure, analyze dependencies, and report architectural health.

Frequently Asked Questions about architecture-audit

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

FAQPage Schema
How do I audit codebase architecture to identify structural drift and coupling issues?

An architecture audit evaluates structural drift by mapping actual code structure against the claimed architecture. It analyzes dependencies, pattern consistency, and cross-cutting concerns to reveal architectural health and identify coupling or cohesion issues.

What is the best way to assess architectural health before a major codebase migration?

Assessing architectural health before a migration involves mapping structure and analyzing dependencies to evaluate refactors. You validate the actual codebase against its stated architecture to measure cohesion, boundaries, and pattern consistency.

Can I use an architecture audit to evaluate dependencies and cohesion in a large codebase?

Yes, an architecture audit applies to codebases of any size to evaluate dependencies and cohesion. It maps structure, analyzes dependency patterns, and assesses cross-cutting concerns to guide governance and onboarding for large projects.

When do I need to validate pattern consistency and boundaries in my codebase?

You validate pattern consistency and boundaries when assessing architectural drift, guiding onboarding, or enforcing governance. Validating these patterns ensures the actual code structure aligns with the stated architecture and maintains proper cohesion.

Does an architecture audit work for evaluating cross-cutting concerns and codebase evolution?

An architecture audit evaluates cross-cutting concerns and codebase evolution by reading actual code. It assesses how the codebase has evolved over time, ensuring structural mapping and dependency analysis align with stated architectural goals.