architecture-reviewer

Detect architecture design issues and generate structured reports with file paths and priorities.

2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/lexicalninja/my-little-scrum-team --skill architecture-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-reviewer
Source: https://github.com/lexicalninja/my-little-scrum-team/tree/main/skills/architecture-reviewer
Command: npx skills add https://github.com/lexicalninja/my-little-scrum-team --skill architecture-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture design issues degrade maintainability, scalability, and clarity in codebases; this skill provides systematic reviews and structured improvement suggestions.

Core Features & Use Cases

  • Structured reviews: Detects separation of concerns violations, tight coupling, missing abstractions, design pattern violations, scalability concerns, and maintainability issues with actionable improvements.
  • Reports with traceability: Returns file paths, line references where applicable, issue type, current design, suggested fixes, rationale, and priority.
  • Use Case: Use on large codebases or monorepos to produce a prioritized list of architectural refactors for better long-term maintainability.

Quick Start

Provide an end-to-end architecture review for the target codebase, listing issues, risks, and recommended improvements.

Frequently Asked Questions about architecture-reviewer

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

FAQPage Schema
How do I detect tight coupling and separation of concerns violations in my codebase?

To detect tight coupling and separation of concerns violations, analyze your modules and dependencies to identify interdependencies and mixed responsibilities. This process reveals missing abstractions and maintainability risks, providing a structured list of architectural flaws for targeted refactoring.

What is an architecture review and how does it improve code maintainability?

An architecture review systematically audits your software design patterns and module structures to uncover maintainability and scalability issues. It produces a prioritized report detailing current design flaws, suggested improvements, and rationale to guide long-term refactoring.

How do I perform an automated architecture audit on a large monorepo?

Perform an automated architecture audit on a monorepo by scanning the entire project for design pattern violations and tight coupling across modules. This generates a prioritized, structured report with file paths and line references to pinpoint exact locations needing architectural refactoring.

Can I get specific file paths and line references when checking for design pattern violations?

Yes, checking for design pattern violations can return specific file paths and line references where applicable. The review maps each identified issue to its exact location, categorizes the architecture flaw, and provides structured suggestions for improvement.

Does this architecture review process work for identifying scalability concerns in existing software projects?

Yes, this architecture review process works for identifying scalability concerns by analyzing dependencies and module structures across existing software projects. It highlights structural bottlenecks and missing abstractions, outputting a prioritized list of risks to ensure future scalability.