architect-review
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
Author
Category
Development ToolsInstall
Hot:2
Download and extract to your skills directory
Copy command and send to OpenClaw for auto-install:
Download and install this skill https://openskills.cc/api/download?slug=sickn33-skills-architect-review&locale=en&source=copy
Architect Review - Software Architecture Review AI Assistant
Skill Overview
Architect Review is an AI architecture assistant well-versed in modern software architecture patterns, focusing on system architecture reviews, scalability assessments, and architectural design guidance to help you build robust, maintainable distributed systems.
Applicable Scenarios
1. System Architecture Review and Design Evaluation
Before making major architectural changes, splitting into microservices, or introducing a new technology stack, use Architect Review to evaluate the soundness of architectural decisions. It can identify potential architectural risks, anti-patterns, and bottlenecks, ensuring designs adhere to best practices.
2. Scalability and Maintainability Analysis
When a system faces performance bottlenecks or accumulating technical debt, Architect Review can perform deep analysis of scalability and maintainability metrics and provide concrete improvement suggestions and refactoring directions.
3. Distributed Systems Architecture Guidance
For engineering teams building microservices, event-driven systems, or cloud-native applications, Architect Review offers end-to-end architectural guidance—from service boundary definition to handling data consistency.
Core Capabilities
1. Comprehensive Architecture Pattern Review
Expert in modern architecture patterns, including Clean Architecture, Hexagonal Architecture, microservices, Event-Driven Architecture (EDA), Domain-Driven Design (DDD), CQRS, etc. It can assess whether your system correctly applies these patterns and identify overdesign or misapplication.
2. Distributed Systems Design Assessment
Covers core design elements of distributed systems such as Service Mesh, event stream processing, distributed data patterns, resilience patterns (circuit breakers, bulkheads, timeouts), distributed caching, load balancing, and helps you build reliable distributed applications.
3. Quality Attributes and Risk Analysis
Evaluates quality attributes like reliability, availability, scalability, security, and maintainability, identifies technical debt and potential risks in the architecture, and provides improvement recommendations with trade-off analysis.
Frequently Asked Questions
What does an architecture review mainly focus on?
An architecture review focuses on multiple quality attributes of the system: scalability (can the system handle future growth), maintainability (is the code easy to understand and modify), reliability (is the system fault-tolerant and highly available), security (are there security vulnerabilities), and architecture pattern compliance (are design patterns and principles applied correctly). Architect Review evaluates comprehensively across these dimensions.
When should I use this skill?
It is recommended to use it proactively in the following scenarios: during the architecture design phase (to validate the reasonableness of designs), during code review (when a PR involves architectural changes), before system refactoring (to assess scope and risk), when introducing new technologies (to analyze impact on the existing architecture), and for performance troubleshooting (to determine if issues are at the architecture level). It is not suitable for simple code style reviews or minor local changes.
What is the difference between architecture review and code review?
Code review focuses on implementation details: code style, naming conventions, correctness, unit test coverage, etc.; architecture review focuses on structure and design decisions: module boundaries, dependencies, data flow, technology choices, scalability, etc. Architect Review specializes at the architecture level. If you only need to check variable naming or function logic, use a conventional code review tool. But when changes involve service boundary adjustments, introducing new architecture patterns, or may affect system scalability, an architecture review is needed.