architecture-assessment

Analyze codebase architecture for patterns, anti-patterns, coupling, and technical debt.

4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/mgd34msu/goodvibes-gemini --skill architecture-assessment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-assessment
Source: https://github.com/mgd34msu/goodvibes-gemini/tree/main/skills/architecture-assessment
Command: npx skills add https://github.com/mgd34msu/goodvibes-gemini --skill architecture-assessment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify and quantify architectural flaws, anti-patterns, and technical debt within a codebase, providing actionable insights for improvement.

Core Features & Use Cases

  • Architecture Evaluation: Assess overall structure, design principles, and quality attributes.
  • Pattern Recognition: Detect and evaluate common architectural patterns (e.g., MVC, Clean Architecture).
  • Anti-Pattern Detection: Identify detrimental patterns like God Classes, Spaghetti Code, and Distributed Monoliths.
  • Coupling & Cohesion Analysis: Measure inter-module dependencies and intra-module focus.
  • Scalability Review: Assess readiness for increased load and traffic.
  • Technical Debt Inventory: Catalog and prioritize various forms of technical debt.
  • Use Case: Before a major refactoring effort, use this Skill to get a comprehensive health report of the existing architecture, pinpointing the riskiest areas and guiding the refactoring strategy.

Quick Start

Perform a comprehensive architecture assessment of this codebase, identifying patterns, anti-patterns, and improvement opportunities.

Frequently Asked Questions about architecture-assessment

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

FAQPage Schema
How do I assess codebase architecture and identify technical debt?

To assess codebase architecture and identify technical debt, evaluate system design principles, detect anti-patterns like God Classes or Spaghetti Code, and catalog debt inventory using structured assessment frameworks and metric collection.

What is coupling and cohesion analysis in software architecture?

Coupling and cohesion analysis measures inter-module dependencies and intra-module focus to evaluate codebase health. It identifies architectural flaws by examining how tightly modules are linked and how well individual components maintain a single, clear purpose.

How do I detect architectural anti-patterns before a major refactoring effort?

Detect architectural anti-patterns before refactoring by performing a comprehensive architecture evaluation. This process identifies detrimental patterns like Distributed Monoliths and Spaghetti Code, pinpointing the riskiest areas to guide your refactoring strategy.

Can I evaluate codebase scalability and readiness for increased traffic?

Yes, you can evaluate codebase scalability readiness by reviewing overall system design and quality attributes. A scalability assessment analyzes architectural patterns and coupling to determine if the current structure can handle increased load effectively.

What is the best way to inventory and prioritize technical debt in a software project?

The best way to inventory technical debt is to catalog various forms of debt within the codebase and quantify architectural flaws. Using structured assessment frameworks helps prioritize these issues based on their impact on system health and scalability.

Does code quality assessment work for recognizing common architectural patterns?

Yes, code quality assessment works for recognizing common architectural patterns by evaluating the overall system structure. It detects and evaluates established design paradigms like MVC or Clean Architecture to determine if they are correctly implemented.