By hand it would easily have taken a day. Claude Code cleared them while they watched TV, and has since added a feature to a Rust editor they don't even know.
“A few weeks ago I used Claude Code to fix 600+ linting errors in 20 year old code, in an evening while watching TV, these easily would have taken a day to do manually.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
Used Claude Code to fix 600+ linting errors in 20-year-old code. They’ve also had it add a feature to the Helix editor, written in Rust, which they don’t know, so it returns you to where you last were in a file, and had Claude build an “rsync for block devices” program.
The lint fixes were done in an evening while they watched TV; by hand, they’d easily have taken a day. The Helix change was built in the background while they worked on something else.
Run [linter] on this codebase and fix every error, one rule at a time. Don't change behaviour: after each batch, run the tests and stop if anything fails. Commit each rule's fixes separately with a short message, and list anything you couldn't fix safely for me to review.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.