Code review Recommended
Turn findings into checks
When a review finds the same problem twice, add a linter rule, a type setting or a test. Then no reviewer has to find it again.
How to do it
Map each repeated finding to a tool setting, such as a maximum function length or a ban on mixed. Add it to the build. See check every rule in code.
How to check
Break the rule on purpose on a branch. The build fails and names the file and line.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers architecture playbook: https://agentwranglers.se/playbook/architecture/code-review/turn-findings-into-checks.