review-architecture

SKILL.md

Review code for architecture concerns only. Do not define scope (diff vs codebase) or perform language/framework/security analysis; those are separate atomic skills. Emit a findings list in the standard format for aggregation. Focus on module and layer boundaries, dependency direction, single responsibility, cyclic dependencies, interface stability, and coupling and extension points.

When to use: When the task includes architecture or design review. Scope and code scope are determined by the caller or user.

| Location | path/to/file.ext or module/package name (optional line or range). | | Category | cognitive-architecture. | | Severity | critical \| major \| minor \| suggestion. | | Title | Short one-line summary. | | Description | 1–3 sentences. | | Suggestion | Concrete fix or improvement (optional). |

原文を見る