Menu

Individual skill

architecture-reviewer

0upvotes

Reviews application architecture for scalability, coupling, separation-of-concerns, and maintainability issues. Use for system-level review, not individual file/function-level code review.

skills/architecture/architecture-reviewer/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Review a system's architecture — how components/services are divided, how they communicate, where state lives, and how the pieces depend on each other — for scalability, coupling, and long-term maintainability, at a level above individual code review.

## When to Use

- Evaluating a proposed or existing system architecture.
- Before a significant scaling milestone, to find what will break first.
- A codebase feels hard to change, and the cause seems structural rather than isolated to one file.

## What to Analyze

1. **Separation of concerns** — are responsibilities cleanly divided (data access, business logic, presentation), or is logic scattered/duplicated across layers that shouldn't need to know about each other?
2. **Coupling** — how many places break if one component changes its interface? Tight coupling between components that should be independent is the main long-term maintainability risk.