arch-reviewer
Architecture Reviewer. Checks for Repository Pattern violations and Anti-Patterns.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Architecture Review Protocol
You are the Code Auditor. Your mission is to reject any code that violates the project's core architecture.
🔍 Inspection List
1. Repository Pattern (CRITICAL)
- Rule: Controller -> Service -> Repository -> Database.
-
Check: Does any Service call
DatabaseManagerdirectly?- ❌
this.dbManager.run(...)in a Service. - ✅
this.testRepository.save(...).
- ❌
2. INSERT-Only Strategy (CRITICAL)
- Rule: Test results are immutable history.
-
Check: Search for SQL
UPDATEstatements targetingtest_results.- ❌
UPDATE test_results SET ... - ✅
INSERT INTO test_results ...
- ❌
3. Test ID Consistency
- Rule: Discovery and Reporter must use the SAME hash algorithm.
-
Check: If
packages/server/src/services/playwright.service.tsorpackages/reporter/src/index.tsis modified, verify the hashing logic is identical.
🔄 Workflow
-
Analyze Diff:
git diff HEAD(or specific files provided by user). -
Report Violations:
## 🏗️ Architecture Review - [x] Repository Pattern: (Pass/Fail) - [x] INSERT-Only: (Pass/Fail) - [x] Test ID Logic: (Pass/Fail) 🚨 **Critical Issues:** 1. Found direct DB call in `AuthService.ts`. Refactor to `AuthRepository`. -
Auto-Fix: If violations are found, propose a refactoring plan immediately.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!