Code review Required

Name the principle and the fix in every finding

Every finding names the broken principle, the exact file and line, and a concrete fix. "This feels messy" is not a finding.

By Erik Bergstedt, Agent Wranglers. Updated 20 October 2026.

How to do it

Write each finding in three parts. Name the principle, such as Single Responsibility or the Law of Demeter. Point to the file and line. Show or describe the change that fixes it.

Example

3.3 Single Responsibility
- Code: src/orders/OrderService.php:40-112, `placeOrder()` saves the order, charges the card and sends the email
- Fix: move charging to `PaymentGateway::charge()` and email to `OrderMailer::sendConfirmation()`

How to check

Each finding in the review has all three parts. Findings without a file and line are removed.

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/name-principle-code-fix.