post-codegen-check

Automated post-codegen quality checks for Rust code are performed by spawning a subagent to review modified .rs files against project standards. This ensures formatting, safety, and documentation requirements are met before reporting changes as complete.

Post-codegen quality checks for Rust code focus on formatting, mutex audit, duplication, documentation, architecture, exhaustiveness, unsafe code, and comment hygiene. These checks ensure modified .rs files meet project standards before completion.

Yes, post-codegen quality checks for Rust code include specific audits for incorrect mutex usage and unsafe code. The review instructions also cover formatting, documentation, architecture, exhaustiveness, and comment hygiene.

Yes, this automated post-codegen checking for Rust code requires no external dependencies. It operates by spawning a subagent and utilizing reference scripts to evaluate modified .rs files against predefined review instructions.

Run the post-codegen-check skill to initiate automated quality assurance on your latest Rust project changes. It requires access to modified .rs files and reads review instructions from its references directory to perform the checks.

Generated Rust code may fail project standards due to formatting errors, incorrect mutex usage, missing documentation, or unsafe code. Automated post-codegen quality checks identify these issues in modified .rs files before they are reported as complete.