You have this line in the default harness, applying a rule about coding: “Write code that reads like the surrounding code: match its comment density, naming, and idiom.” It sounds good, in principle, but there’s a pretty bad failure mode: Suppose there’s a new file. Say, it starts with one line of code and a large, 20-line comment that it needs for some reason. This happens occasionally. Or something similar, where a few lines have long comments that are needed. Often it’s not even the same type of file as the rest of the code. Then a subsequent task, later, adds 10 lines of code to it. You know what happens? Each of those lines of code gets their own 20-line comment, regardless of the need for it. Now we have hundreds of lines of totally unnecessary comments bloating the file, going stale, giving bad information to agents, until the user removes it. I am not going to say I know what a better solution is, due to how impactful each word in the default harness is, but I’m sure there’s a better line submitted by /u/Fragsworth
Originally posted by u/Fragsworth on r/ClaudeCode