Review architecture
Reviews the structural quality of code. Use when reviewing structural changes in a diff, checking a new or edited module boundary, or auditing the architecture of a codebase.From its SKILL.md
npx -y skills add mrinalwadhwa/fluent --skill review-architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.5 KB, as published. Nobody here has run it
Purpose
Decide whether the code's architecture is fit to ship. Identify improvements that would make the codebase simpler, more coherent, and easier to change.
Scope
The invoking layer decides what's in scope. For a diff-scoped review, that's the structural choices in the diff. For a full-codebase audit, that's the codebase's overall structure. Even in a diff-scoped review, evaluate the changes in the context of the entire codebase — a boundary that looks fine in isolation can be wrong in context. Check each choice for structural quality and check the codebase as a whole for coherence.
Method
-
Read the code under review to understand its structure — module boundaries, key abstractions, dependencies.
-
Read
references/architecture.mdfor architectural principles. Read any related guides it points to for the code under review. -
For each in-scope structural choice:
- Evaluate against the principles in
references/architecture.md. - Identify improvements.
- Evaluate against the principles in
-
Check for anti-patterns from
references/architecture.md. -
For each improvement, decide if it blocks shipping. Circular dependencies, god objects, and coupling that will block near-term work typically block. Small simplifications, naming preferences, and style choices typically don't.
The invoking layer may add checks in addition to those above.