dev-ui-review

A structured UI code review evaluates code correctness, cleanup, and documentation across UI lessons. It coordinates phase-based agent reviews to analyze common/ui code and lesson mains, producing a comprehensive report of hotspots requiring scrutiny before the final pass.

Static analysis for UI lesson code checks for memory safety, parameter validation, bug detection, and undefined behavior. It also enforces explicit checks for resource cleanup, test verifications, and documentation consistency across common/ui components and lesson mains.

You run phase-based checks sequentially using a Task agent for builds, tests, and linting. This parallel agent-driven workflow assesses code correctness, cleanup, and documentation, repeating until no findings remain and a consolidated report is produced.

Yes, automated agent workflows support UI quality assurance and linting by applying parallel checks across UI contexts. They identify hotspots requiring scrutiny and enforce explicit validations for parameter handling, resource cleanup, and test verifications.

You need a pre-final pass UI quality review before releasing UI lessons across a repository. It catches code quality, correctness, and documentation issues early by analyzing common/ui code and lesson mains to identify hotspots requiring scrutiny.

The best way to consolidate UI code quality and correctness checks is a phase-based review workflow. It coordinates parallel agent reviews covering memory safety, bug detection, and documentation consistency, producing a comprehensive report for fixes.