architecture-review-lens

Solid

Use when a diff may break system boundaries, dependency direction, or cross-service contracts — fifth judge dispatched by /review-changes alongside the four standard judges.

AI & Automation 7 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
30
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# architecture-review-lens > Fifth judge in the `/review-changes` family. Reviews a diff for > **architectural fit**, not correctness, security, tests, or style. > Catches what the other four miss: layer violations, wrong > dependency direction, leaking abstractions, and broken cross-service > contracts. Sibling of [`judge-bug-hunter`](../judge-bug-hunter/SKILL.md) > et al. — never overlaps. ## When to use - `/review-changes` dispatches its "architecture" slice to this skill. - A reviewer asks "does this belong here?", "should this be in the domain layer?", or "is this leaking storage details?". - A diff adds a cross-service call, event, or contract. Do NOT use when: - The diff is documentation-only or a formatting-only change. - The concern is correctness — route to [`judge-bug-hunter`](../judge-bug-hunter/SKILL.md). - The concern is security — route to [`judge-security-auditor`](../judge-security-auditor/SKILL.md). - The concern is naming or DRY — route to [`judge-code-quality`](../judge-code-quality/SKILL.md). - The concern is *whether to make* the architectural change — route to [`decision-record`](../decision-record/SKILL.md) first. ## Procedure ### 1. Anchor on the system shape Read the codebase's stated architecture (ADRs, AGENTS.md, module docs). If no shape is documented, infer it from folder structure and surface the gap. You are judging the diff against **the stated shape**, not a fantasy ideal. ### 2. Inspect each changed file for fit For every...

Details

Author
event4u-app
Repository
event4u-app/agent-config
Created
3 months ago
Last Updated
today
Language
TypeScript
License
MIT

Bundled in these plugins

agent-config

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

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.

0 Updated today
itzikiusa
Code & Development Listed

judge-overengineering-review

Over-engineering review checklist the parent runs before declaring non-trivial code changes done.

20 Updated today
Pythoughts-labs
Code & Development Listed

architecture-review

Review module boundaries, dependency direction, contracts, migration risk, and fit to the product architecture.

4 Updated today
jsuvic