意図的な設計判断をレビュアーが誤検知(FP)しないよう、全 review-*.md に
{report:coder-decisions.md} の参照セクションを追加。ただし設計判断自体の
妥当性も評価する指示を含め、盲目的な通過を防ぐ。
1.0 KiB
1.0 KiB
Review the changes from a frontend development perspective.
Review criteria:
- Component design (separation of concerns, granularity)
- State management (local vs. global decisions)
- Performance (re-renders, memoization)
- Accessibility (keyboard navigation, ARIA)
- Data fetching patterns
- TypeScript type safety
Note: If this project does not include a frontend, proceed as no issues found.
Design decisions reference: Review {report:coder-decisions.md} to understand the recorded design decisions.
- Do not flag intentionally documented decisions as FP
- However, also evaluate whether the design decisions themselves are sound, and flag any problems
Judgment Procedure
- Review the change diff and detect issues based on the frontend development 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, judge as REJECT