跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

architecture-reviewer

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

codebygarv · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add codebygarv/Ai-skills --skill architecture-reviewer

技能说明


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

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.
  3. Scalability — what's the first component to become a bottleneck under significantly more load/data, and is that dependency structural (hard to fix later) or incidental (easy to fix later)?
  4. Data flow & state ownership — is it clear which component owns a given piece of state/data, or is the same data mutated from multiple places with no clear source of truth?
  5. Failure isolation — does one component's failure cascade to unrelated components, or is blast radius contained?
  6. Evolvability — how hard is it to add a plausible near-future requirement (a new integration, a new client type) given the current structure?

Output Format

  • A short description of the architecture as understood, to confirm shared understanding before critiquing it.
  • Findings grouped by area (Separation of Concerns, Coupling, Scalability, Data Ownership, Failure Isolation, Evolvability).
  • Each finding: the structural issue, the concrete scenario where it causes pain, and a directionally concrete recommendation (not just "reduce coupling" — name the specific boundary to introduce).
  • Distinguish issues worth fixing now vs. acceptable technical debt given current scale/priorities.

Avoid

  • Recommending a full rewrite or fashionable pattern (microservices, event sourcing) without justifying it against the system's actual scale and team size.
  • Flagging coupling that's actually appropriate for the current scale (premature decoupling has its own real costs).
  • Reviewing at the file/function level — that's Code Reviewer's job; stay at the component/service/system level here.