architecture-review

Identify architectural issues in code changes across multi-service architectures.

1|Updated Apr 24, 2026

Search Tags:#architecture #maintainability #governance #review #coupling #design-patterns #api-contracts

Ready to run

npx skills add https://github.com/NoSugarCoffee/dotai --skill architecture-review-nosugarcoffee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/NoSugarCoffee/dotai/tree/main/skills/architecture-review
Command: npx skills add https://github.com/NoSugarCoffee/dotai --skill architecture-review-nosugarcoffee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture review identifies design issues and drift early in code changes to preserve system evolvability.

Core Features & Use Cases

Design pattern compliance checks to ensure proper abstractions, boundaries, and layering.
Separation of concerns validation to keep business logic isolated from infrastructure and UI concerns.
API contract validation to detect breaking changes and enforce stable interfaces across services.
Cross-service dependency assessment to minimize coupling and promote modular evolvability.
Use cases include architectural reviews of major PRs, onboarding new engineers, and governance over evolving systems.

Quick Start

Perform an architectural assessment of the latest changes, focusing on boundaries, contracts, and coupling.

Frequently Asked Questions about architecture-review

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

FAQPage Schema

How do I detect API contract drift and layer violations during code reviews?▼

Architecture review identifies design issues and drift early in code changes by checking design pattern compliance, separation of concerns, and API contracts to preserve system evolvability.

How do I assess cross-service dependencies to minimize coupling in multi-service architectures?▼

Assess cross-service dependencies by evaluating coupling and design boundaries across multi-service architectures to minimize unintended dependencies. This validation promotes modular evolvability and maintains structural governance over evolving systems.

What is architecture review and when do I need it for evolving systems?▼

Architecture review identifies design issues and drift early in code changes by checking design pattern compliance, separation of concerns, and API contracts to preserve system evolvability. You need it for major PRs, onboarding new engineers, and governing evolving systems.

Can I validate separation of concerns to keep business logic isolated from infrastructure?▼

Yes, you can validate separation of concerns to keep business logic isolated from infrastructure and UI concerns. This ensures proper abstractions, boundaries, and layering are maintained across multi-service architectures during code reviews.

Does architecture review work for governance over evolving multi-service architectures?▼

Yes, architecture review works for governance over evolving multi-service architectures by applying design pattern checks and cross-service dependency assessment. It detects layer violations and contract drift to enforce stable interfaces across services.

What are the limitations of automated architecture review for design pattern checks?▼

Automated architecture review focuses strictly on structural design boundaries, contracts, and coupling rather than runtime behavior or performance. It serves as a guardrail for maintainable evolution but does not replace deeper functional testing or operational monitoring.