architecture-audit

Audit codebases to verify architectural claims against actual implementation.

5|1|Updated Feb 7, 2026

Search Tags:#architecture #codebase #audit #pattern #drift #dependency

Ready to run

npx skills add https://github.com/boparaiamrit/skills-by-amrit --skill architecture-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-audit
Source: https://github.com/boparaiamrit/skills-by-amrit/tree/main/skills/architecture-audit
Command: npx skills add https://github.com/boparaiamrit/skills-by-amrit --skill architecture-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits the architecture of a codebase to ensure the implemented structure matches stated architectural goals, surfacing drift and hardening future maintainability.

Core Features & Use Cases

Structure mapping and pattern identification across modules.
Dependency and coupling analysis with actionable recommendations.
Use Case: before a major refactor, run an architecture audit to surface hotspots and plan a safe migration.

Quick Start

Analyze a given codebase by initiating an architecture-audit pass to compare claimed architecture with code, identify dependencies, and generate a prioritized improvement plan.

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 find structural drift?▼

To audit codebase architecture, you compare claimed architecture against the actual implementation to identify structural drift, mapping module patterns and dependencies to surface hotspots for a prioritized improvement plan.

When do I need to run an architecture audit on my codebase?▼

You need an architecture audit before major refactors or migrations to assess structure, coupling, cohesion, and drift across components, ensuring the implemented codebase matches your stated architectural goals.

How do I analyze codebase dependencies and coupling before a refactor?▼

You analyze codebase dependencies and coupling by mapping module boundaries and generating dependency graphs to measure coupling metrics, which yields actionable recommendations for a safe migration.

Can I assess architectural drift in large evolving codebases?▼

Yes, you can assess architectural drift in large or evolving codebases by verifying architectural claims against the implementation, requiring clear module boundaries and measurable metrics to produce actionable recommendations.

What is the best way to surface codebase debt and coupling hotspots?▼

The best way to surface codebase debt and coupling hotspots is to execute an architecture audit pass that compares stated architecture with code, identifying dependency patterns and prioritizing structural improvements.