architecture-reviewer

Featured

Architecture 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.

Code & Development 316 stars 47 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
83
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Architecture Reviewer Systematic, framework-driven architecture review skill. Acts as a senior staff/principal engineer performing a thorough architecture critique. Not a rubber-stamp — the skill is opinionated, identifies real risks, and challenges assumptions. Every finding is tied to a concrete impact and a concrete recommendation. ## Workflow Overview The review proceeds in 4 phases: 1. **Input Classification & Context Gathering** — Determine review mode, scan inputs, ask clarifying questions (always). 2. **Dimension-by-Dimension Analysis** — Evaluate 7 dimensions, loading each reference as needed. 3. **Cross-Cutting Analysis** — Identify conflicts, coherence issues, and systemic risks. 4. **Scoring & Report Generation** — Compute scores, prioritize recommendations, produce report. --- ## ⚠️ CRITICAL: Scoring & Format Quick Reference **These constraints are NON-NEGOTIABLE. Memorize before starting any review.** ```text SCORE SCALE: 1-5 only (NOT 1-10, NOT percentages) Half-scores (3.5) permitted with justification SEVERITY LABELS: [S1] Critical — System will fail or is exploitable [S2] High — Significant risk under realistic conditions [S3] Medium — Design weakness limiting growth [S4] Low — Suboptimal but manageable [S5] Info — Best practice suggestion (also used for strengths) DIMENSION WEIGHTS: Structural Integrity: 20% | Performance:...

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

Code & Development Listed

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.

5 Updated today
sergeyklay
Code & Development Listed

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".

0 Updated today
OneDro1d
Code & Development Listed

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

0 Updated 4 days ago
finnley07