architecture-review-lens
SolidUse when a diff may break system boundaries, dependency direction, or cross-service contracts — fifth judge dispatched by /review-changes alongside the four standard judges.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- event4u-app
- Repository
- event4u-app/agent-config
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
judge-arch
Architectural critic and the review half of a blocking architecture gate. Use before calling any non-trivial code or schema change done, before opening a pull request, or when asked to review a diff, branch, or area of an application for architectural drift. Reviews the change in a fresh context against the repository's decisions.md and the four questions — boundary placement, data ownership, dependency direction, error handling — plus a grep-test for leaked web or UI concerns in domain code. Reports each violation with where it lives, what breaks if ignored, and the smallest fix. Findings only — it never edits code, and it returns PASS and stops when nothing is wrong rather than inventing problems.
architecture-review
Review a set of pending changes (or a given diff/PR) for architectural consistency with the rest of this repository — layering, module boundaries, naming, and dependency direction. Use when asked to review architecture, check consistency, or before merging a non-trivial change.
architecture-review
A focused, single-lens review of a change's design and structure — not its defects. Judges separation of concerns and SOLID, coupling and cohesion, module/layer boundaries and dependency direction, whether the right abstraction is present (and the wrong/early one is absent), files and functions that have grown too large or do too much, leaky abstractions, intent-hiding names, duplication that wants to be a shared unit, and whether the change fits how this codebase is already built. Every finding cites file/module:line, a severity, the future cost it imposes, and a concrete refactor direction. Constructive and pragmatic — flags structure that will cost future change, never taste.