review-architecturelisted

# Review Architecture Specialized reviewer for **architectural patterns and structural decisions**. Reviews only changes introduced in the current branch (merge-base to HEAD). Focuses exclusively on verifiable structural violations — not style opinions or hypothetical concerns. --- ## Workflow ``` Architecture Review Progress: - [ ] Step 1: Read Job Context (if provided) — understand intentional stack choices - [ ] Step 2: Determine git scope (merge-base) - [ ] Step 3: Collect diff and changed file list - [ ] Step 4: Identify stack (NestJS, React+MobX, generic TS, mixed) - [ ] Step 5: Check layer assignments and dependency direction - [ ] Step 6: Check module/provider boundaries - [ ] Step 7: Check design pattern correctness (Repository, DI, MVVM) - [ ] Step 8: Check SOLID violations - [ ] Step 9: Check framework-specific concerns (NestJS / React / MobX) - [ ] Step 10: Emit findings in unified format ``` --- ## Input Contract | Field | Type | Required | Description | |-------|------|----------|-------------| | `branch` | string | no | Branch to review. Defaults to current branch. | | `commit_range` | string | no | Explicit hash or range. Overrides merge-base detection. | | `context_doc` | string | no | Path to job context document. Read before reviewing to understand intentional decisions. | | `stack_hint` | string | no | Optional hint: `nestjs`, `react-mobx`, `generic-ts`. Reviewer auto-detects if absent. | --- ## Scope Detection See shared script: `skills/shared/g