architecture-audit

Name: architecture-audit
Availability: InStock
Author: kaptinlin

Audit Go codebases for circular dependencies, fat interfaces, and spec drift.

23|2|Updated Jun 9, 2025

Search Tags:#architecture #codebase #dependencies #audit #go #quality #specs-alignment

Ready to run

npx skills add https://github.com/kaptinlin/gozod --skill architecture-audit-kaptinlin

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architecture-audit provides a systemic review of a codebase to detect architectural issues like circular dependencies, fat interfaces, and cross-layer violations, enabling proactive health maintenance before problems escalate.

Core Features & Use Cases

Seven-phase systematic review covering code quality, dependency analysis, interface health, abstraction consistency, pattern consistency, quantitative metrics, and SPECS alignment.
Detects circular dependencies, layer boundary violations, and interface bloat to guide refactors and architectural decisions.
Use cases include baseline health assessment before major releases, ongoing architectural governance, and SPECS drift detection across modules.

Quick Start

Run the architecture-audit workflow to generate a comprehensive health report and action plan for your repository.

Frequently Asked Questions about architecture-audit

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

FAQPage Schema

How do I detect circular dependencies in a Go codebase?▼

Detect circular dependencies in a Go codebase by running a systematic architecture audit that analyzes import graphs to identify structural issues. This allows you to proactively map dependency cycles and guide refactoring efforts before they escalate.

What is a codebase architecture audit and when do I need one?▼

A codebase architecture audit is a systemic review that detects structural issues like fat interfaces and cross-layer violations. You need this health check before major releases or during refactors to identify spec drift and architectural decay.

What's the best way to check for spec drift before a software release?▼

The best way to check for spec drift before a release is to perform a SPECS alignment phase within a multi-phase architecture audit. This systematically compares your codebase implementation against specifications to detect deviations and ensure consistency.

Can I audit interface health and abstraction consistency in a large Go project?▼

Yes, you can audit interface health and abstraction consistency in a large Go project by applying a systematic review methodology. This detects interface bloat and cross-layer violations, enabling proactive health maintenance and architectural governance.

How do I run a code quality baseline assessment for a repository?▼

Run a code quality baseline assessment by initiating an architecture audit workflow that establishes a quantitative metrics baseline. This generates a comprehensive health report covering code quality, dependencies, and pattern consistency for your repository.

How does a seven-phase architecture audit identify cross-layer violations?▼

A seven-phase architecture audit identifies cross-layer violations by systematically analyzing dependency structures, interface health, and pattern consistency. This detects boundary breaches across modules to guide refactors and enforce architectural governance.