review-code-idiom-check

<when_to_use> The team wants a unified engineering style and predictable patterns The PR uses atypical constructs for the current stack </when_to_use>

<input_requirements> PR/diff Module language and framework Project-local conventions </input_requirements>

<core_checks> Selected patterns match standard language/framework practices Common APIs and lifecycles are used, with no workarounds without reason Exceptions to idioms are explicitly justified in comments or PR description Code is consistent with the rest of the codebase in similar areas </core_checks>

<quality_rules> Idiomatic style must not degrade correctness or security Idiom suggestions include a short replacement example Project-local conventions take priority over general recommendations </quality_rules>

<do_not> Do not require rewriting working code for abstract aesthetics Do not propose a new paradigm without proven team benefit </do_not>

<output_requirements> List of idiom deviations: what, why, and minimal fix approach Separate blocking and advisory findings </output_requirements>