architecture-reviewer
FeaturedArchitecture reviews across 7 dimensions (structural, scalability, enterprise readiness, performance, security, ops, data) with scored reports. Triggers on: "review architecture", "critique design", "audit system", "assess scalability", "enterprise readiness", "technical due diligence". NOT for diagrams, use architecture-diagram.
Install
Quality Score: 93/100
Skill Content
Details
- Author
- Mathews-Tom
- Repository
- Mathews-Tom/armory
- Created
- 6 months ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
review-arch
Conduct a principal-level architecture review of a system, specification, diagram, or set of design decisions. Use when asked to review an architecture, evaluate a design, assess coupling/cohesion, check for anti-patterns, audit system boundaries, or produce an Architecture Review Board (ARB) style verdict. Also use when someone says 'review this architecture', 'is this design sound', 'what's wrong with this topology', 'evaluate these tradeoffs', or 'audit this system'. Produces a structured verdict organized around critical risks, significant concerns, observations, strengths, and open questions, grounded in evidence from the codebase and cited against established methodology (ATAM, ISO/IEC 25010, documented anti-pattern catalogues). Do NOT use for line-by-line code review, spec-vs-implementation verification, or PR-level correctness checks. Name the system, spec, or design to be reviewed in the arguments; the skill does not infer the target from the conversation.
architecture-reviewer
Review architectural changes for coupling, blast radius, and long-term impact. Use when evaluating system design changes, cross-service dependencies, API changes, or infrastructure modifications. Triggers on "architecture review", "impact analysis", "blast radius", "coupling review", "dependency analysis", "breaking change", "migration review", "system design review".
architecture-review
Runs a structured architecture-quality review of a system's module/service boundaries, coupling, data ownership, communication patterns, resilience, structural scalability, extensibility, documentation, pattern consistency, and versioning — evaluating structural soundness and evolvability of the design, not line-level code correctness and not measured runtime performance — then reports the results as one table (check, area, status, evidence, recommendation). Covers domain-aligned vs. arbitrary module boundaries, circular dependencies between modules/packages/services, coupling (does a change in one module ripple into unrelated ones), layering violations (a lower layer reaching up, or a domain layer importing from presentation), data ownership per service vs. shared-database distributed-monolith anti-patterns, cross-boundary consistency (sagas, eventual consistency, distributed transactions), sync-vs-async communication choices and single-points-of-failure created by synchronous call chains, event/message cont