# Turning a repeated review finding into a written rule didn’t stop it coming back. What actually works for you? — retained record

> Retained reddit record from reddit:ClaudeCode.

Canonical: https://highsignal.app/data/records/c02764b9111fdee6

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ClaudeCode)  published 2026-11-02 07:38 ingested 2026-11-03 02:42

[original source ↗](https://www.reddit.com/r/ClaudeCode/comments/1xlr0pk/turning_a_repeated_review_finding_into_a_written/)

## retained text



```
I use Claude Code on an iOS app with a spec, implement and review pipeline. Review findings go in a log, and when a type of finding shows up a second time, it becomes a written rule in the docs the implementer reads.

This helps, but it isn’t enough. One category, dead code left in the diff, has now been logged 5 times and came back even after it became a rule. In one case a leftover `layoutIfNeeded()` was only found by deleting it, and the tests stayed green either way.

So a rule in a markdown file seems to work for some things and not others. For those of you running something similar, which rules did you move out of the docs and into a hook, a linter or a test? Which ones are still just text, and do they hold?
```



document fetched 2026-11-03 00:42 · canonical https://reddit.com/r/ClaudeCode/comments/1xlr0pk/turning_a_repeated_review_finding_into_a_written
