diyu-frontend-reviewer

Review frontend PRs for XSS and accessibility by applying a four-quadrant framework covering Security, Architecture, Quality, and Accessibility. This identifies SSR/RSC boundary risks, API client integrity gaps, and a11y compliance issues before merging.

A four-quadrant frontend review systematically evaluates pull requests across Security, Architecture, Quality, and Accessibility. You need it when merging changes to frontend/ directories to ensure governance alignment and produce traceable remediation reports.

Check SSR and RSC boundary security by reviewing frontend changes against package boundaries and API client integrity. This process identifies server-side rendering risks and reports them in a structured, traceable format for security teams.

Yes, frontend review works with Turbo package boundaries by explicitly checking API client integrity and cross-package dependencies. It evaluates changes affecting frontend/ directories to ensure architectural compliance within monorepo setups.

Generate traceable governance reports by applying metadata-driven discovery to frontend changes and outputting findings across security, architecture, quality, and accessibility. This produces a structured report aligned with governance requirements for code review teams.