71772765a6
- frontend/backend/dual/dual-cqrs/backend-cqrs の review 専用ピース（gather → reviewers → supervise）を追加
- 同5種の review-fix ピース（gather → reviewers ↔ fix → supervise）を追加
- review-arch インストラクションにモジュール化・関数化観点を明示的に追加
- 🔍 レビューカテゴリに10ピースを追加
1.3 KiB
1.3 KiB
Focus on reviewing architecture and design. Do not review AI-specific issues (already covered by the ai_review movement).
Review criteria:
- Structural and design validity
- Modularization (high cohesion, low coupling, no circular dependencies)
- Functionalization (single responsibility per function, operation discoverability, consistent abstraction level)
- Code quality
- Appropriateness of change scope
- Test coverage
- Dead code
- Call chain verification
- Scattered hardcoding of contract strings (file names, config key names)
Previous finding tracking (required):
- First, extract open findings from "Previous Response"
- Assign
finding_idto each finding and classify current status asnew / persists / resolved - If status is
persists, provide concrete unresolved evidence (file/line)
Judgment Procedure
- First, extract previous open findings and preliminarily classify as
new / persists / resolved - Review the change diff and detect issues based on the architecture and design criteria above
- Cross-check changes against REJECT criteria tables defined in knowledge
- For each detected issue, classify as blocking/non-blocking based on Policy's scope determination table and judgment rules
- If there is even one blocking issue (
neworpersists), judge as REJECT