---
title: "Comment by Yunus Emre Vurgun on \"AI Coding Tip 041 - Turn Every Review Finding Into a Rule\" | Hashnode"
description: "One thing that helps rules stay useful: store each rule with the review finding that created it, plus a tiny example of the bad code. When an agent breaks a rul"
url: "https://hashnode.com/posts/ai-coding-tip-041-turn-every-review-finding-into-a-rule/6ad39f210bb21b4bfe4c0205/comment/6ad458b014ee79bfe979a77a"
---

[Discussion](https://hashnode.com/posts/ai-coding-tip-041-turn-every-review-finding-into-a-rule/6ad39f210bb21b4bfe4c0205)

Comment [AI Coding Tip 041 - Turn Every Review Finding Into a Rule](https://hashnode.com/posts/ai-coding-tip-041-turn-every-review-finding-into-a-rule/6ad39f210bb21b4bfe4c0205)

[Yunus Emre Vurgun](https://hashnode.com/@yunusemrevurgun)

[Oct 18](https://hashnode.com/posts/ai-coding-tip-041-turn-every-review-finding-into-a-rule/6ad39f210bb21b4bfe4c0205/comment/6ad458b014ee79bfe979a77a)

One thing that helps rules stay useful: store each rule with the review finding that created it, plus a tiny example of the bad code. When an agent breaks a rule later, you can tell whether the rule was unclear or simply ignored, and rules with no linked finding in months are good candidates to delete. It also keeps the rulebook from growing into a wall of text the model only half reads.
