architecture-review

Name: architecture-review
Availability: InStock
Author: sbknana

Identify architectural issues in code changes across multiple files.

10|4|Updated Feb 5, 2026

Search Tags:#architecture #anti-patterns #code-review #system-design #solid-principles #dependency-direction

Ready to run

npx skills add https://github.com/sbknana/equipa --skill architecture-review-sbknana

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/sbknana/equipa/tree/main/skills/code-reviewer/skills/architecture-review
Command: npx skills add https://github.com/sbknana/equipa --skill architecture-review-sbknana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic architectural review of code changes helps teams identify maintainability risks, coupling, and anti-patterns before merge.

Core Features & Use Cases

Architecture-focused evaluation of changes that add new modules, modify interfaces, or introduce dependencies.
Checks for dependency direction, separation of concerns, SOLID principles, and common anti-patterns.
Use Case: during a PR spanning multiple packages, run architecture-review to surface design issues and remediation guidance.

Quick Start

Analyze the latest pull request by running architecture-review to generate a prioritized list of architectural issues and recommended fixes.

Frequently Asked Questions about architecture-review

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

FAQPage Schema

How do I review system design and check SOLID principles in a pull request?▼

To review system design and check SOLID principles in a pull request, analyze dependency direction, separation of concerns, and anti-patterns to ensure maintainability. This process surfaces architectural issues across new modules and multi-file dependencies before merge.

What is architectural code review and when do I need it for my codebase?▼

Architectural code review is a systematic evaluation of code changes to identify maintainability risks and coupling. You need it when a pull request adds new modules, modifies interfaces, or introduces new dependencies across multiple files.

Can I detect anti-patterns and dependency direction issues across multiple packages?▼

Yes, you can detect anti-patterns and dependency direction issues across multiple packages by applying a structured architectural checklist. This evaluates dependency direction and separation of concerns to surface design issues and provide remediation guidance.

What is the best way to identify maintainability risks before merging code changes?▼

The best way to identify maintainability risks before merging is to run a systematic architectural review on code changes. This generates a prioritized list of architectural issues and recommended fixes, ensuring extensibility and safe code.

What are the limitations of using a structured checklist for architectural review?▼

The limitations of using a structured checklist for architectural review include its restricted scope to dependency direction, SOLID compliance, and separation of concerns. It targets structural design issues and may not address runtime performance or security vulnerabilities.