dev-final-pass

Run a systematic quality review on your lesson directory to identify publication-blocking issues. It applies standardized checks across GPU, math, engine, UI, physics, audio, and asset pipeline tracks to enforce coding conventions and required files.

A lesson PR quality review checks for explicit required files, coding conventions, resource cleanup, naming standards, and documentation accuracy. These checks are derived from recurring themes in the project's historical pull request review feedback.

Yes, you can apply an automated code review to GPU and physics lesson tracks. The review scope covers multiple lesson types, ensuring resource cleanup and naming conventions are met before you create a pull request.

The best way to ensure documentation accuracy is running a final quality pass that validates docs against project standards. It cross-references requirements defined by historical PR feedback to catch recurring documentation errors.

Your lesson pull request fails the final quality pass due to missing required files, improper naming, incomplete resource cleanup, or inaccurate documentation. The review generates a concise, actionable summary of pass/fail results per section to guide remediation.

Yes, the lesson quality review supports C code and asset pipeline tracks. It applies a standardized set of end-to-end checks to these tracks, enforcing coding conventions and required files as defined by project PR history.