architect-review

Reviews system designs and code changes for architectural integrity, scalability, and maintainability.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Tgoldi/claude-skills --skill architect-review-tgoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-review
Source: https://github.com/Tgoldi/claude-skills/tree/main/architect-review
Command: npx skills add https://github.com/Tgoldi/claude-skills --skill architect-review-tgoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Making sound architectural decisions for complex distributed systems is hard, and design flaws often surface only after costly implementation. This Skill provides expert-level architectural review of system designs and code changes before problems reach production. ## Core Features & Use Cases - Architecture Review: Evaluates designs against clean architecture, microservices, event-driven, and DDD patterns, flagging violations and anti-patterns. - Quality Attribute Assessment: Analyzes scalability, resilience, security, and maintainability impacts with High/Medium/Low risk ratings. - Decision Documentation: Produces Architecture Decision Records (ADRs) and concrete refactoring recommendations with tradeoffs. - Use Case: Before merging a change that adds event sourcing to your platform, ask for an architectural review to assess bounded context boundaries, data consistency implications, and migration risks. ## Quick Start Ask the architect to review your proposed microservice design for proper bounded context boundaries and scalability risks.

Frequently Asked Questions about architect-review

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

FAQPage Schema
How do I review a microservices architecture design?

Provide the system context, goals, and constraints, then request an architectural review. The review evaluates service boundaries, bounded contexts, data isolation, and communication patterns, returning risk-rated findings with specific refactoring recommendations.

What architecture patterns does this review cover?

The review covers clean architecture, hexagonal architecture, microservices, event-driven architecture with event sourcing and CQRS, domain-driven design, serverless patterns, and API-first design with REST, GraphQL, and gRPC.

When should I not use an architectural review?

Skip it for small, localized code changes without architectural impact, such as single-module fixes. It is also unsuitable when you lack system context or requirements, since meaningful design assessment depends on that information.

Can it assess event-driven and distributed system designs?

Yes. It evaluates event streaming with Kafka or Pulsar, Saga and Outbox patterns, circuit breakers, distributed caching, and service mesh setups, identifying decoupling and consistency issues in event-driven designs.

Does the review produce architecture decision records?

Yes. Significant decisions are documented as Architecture Decision Records (ADRs) along with C4-model-oriented documentation guidance, assumptions, dependencies, and follow-up validation steps.