dev-final-pass

To automate a quality review pass before a PR submission, provide the lesson number or name to trigger end-to-end checks across README.md, main.c, and CMakeLists.txt files, generating an actionable findings report.

Checking lesson PR readiness across GPU, math, engine, UI, physics, and asset-pipeline tracks requires verifying required files and coding conventions against historical PR feedback to produce a clear pass/fail summary.

You can enforce documentation and coding conventions automatically before publishing by running systematic checks that compare lesson assets and files against project standards and recurring historical PR feedback.

A pre-submission lesson review catches recurring PR feedback issues by centralizing historical project standards into a reproducible workflow, verifying required files and conventions to reduce human error during review.

Yes, you need to provide the lesson number or name as input to run the end-to-end quality checks and generate the actionable pass/fail summary for the /dev-create-pr workflow.

When checking asset-pipeline and CMakeLists.txt files for lesson publishing, the review is limited to verifying consistency with project standards and historical PR feedback, producing actionable issues rather than auto-fixing them.