I noticed very often when proposing changes to the existing code, Claude Dev simply uses the line // ... [rest of the file content remains unchanged until the writeToFile method] to replace a large chunk of original code that is not supposed to be removed. This behavior is often seen in sonnet 3.5 api from my experience, but for Claude Dev's use case this has to be changed. Similarly sonnet 3.5 also tends to remove existing comments which I also find counter-productive. Hence I added two additional rules to counter these behaviors.
I noticed very often when proposing changes to the existing code, Claude Dev simply uses the line
// ... [rest of the file content remains unchanged until the writeToFile method]
to replace a large chunk of original code that is not supposed to be removed. This behavior is often seen in sonnet 3.5 api from my experience, but for Claude Dev's use case this has to be changed. Similarly sonnet 3.5 also tends to remove existing comments which I also find counter-productive. Hence I added two additional rules to counter these behaviors.