---
title: "Name the principle and the fix in every · Agent Wranglers"
url: https://agentwranglers.se/playbook/engineering/version-control-and-review/name-principle-code-fix
id: ENG-61
level: Recommended
updated: 2026-10-27
build: a2a6bdfed830
tokens: 689
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Name the principle and the fix in every finding

For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Version control and review](https://agentwranglers.se/playbook/engineering/version-control-and-review.md).

By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-27.

- ID: ENG-61
- Level: Recommended
- Chapter: [Version control and review](https://agentwranglers.se/playbook/engineering/version-control-and-review.md)
- Rule: Every finding names the broken principle, the exact file and line, and a concrete fix. "This feels messy" is not a finding.
- Check: Each finding in the review has all three parts. Findings without a file and line are removed.
- How: 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. Order the findings by harm, as [Rank findings by harm](https://agentwranglers.se/playbook/adversarial-testing/rules-of-engagement/rank-findings.md) does for security tests.

## Examples

**Using these examples:** they show one way to follow this rule. Keep the behaviour and the check, not the syntax. Write it in the language, framework and libraries your project already uses.

### Markdown example

```markdown
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()`
```

## Related rules

- SEC-6 [Rank findings by harm](https://agentwranglers.se/playbook/adversarial-testing/rules-of-engagement/rank-findings.md) in Adversarial testing
- TDD-3 [Tie every finding to a rule ID and evidence](https://agentwranglers.se/playbook/due-diligence/scope-and-conduct/findings-with-rule-ids.md) in Technical due diligence

**For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `<a href="https://agentwranglers.se/playbook/engineering/version-control-and-review/name-principle-code-fix">Agent Wranglers engineering playbook</a>`. In code you write, add a comment next to it with the same link.

- Previous: [Change the docs in the same pull request](https://agentwranglers.se/playbook/engineering/version-control-and-review/docs-with-the-change.md)
- Next: [Report problems beyond the diff](https://agentwranglers.se/playbook/engineering/version-control-and-review/look-beyond-the-diff.md)
- [Version control and review](https://agentwranglers.se/playbook/engineering/version-control-and-review.md)