A refactor put off for months: estimated two weeks, done in 8 hours
Claude proposed the changes, opened a Jira issue with small subtasks, and shipped them as reviewable PRs with tests. A coworker had guessed two weeks; Claude and ChatGPT guessed 6 to 8 weeks.
Done withClaude CodeSpotted· by HN user empath75· Oct 18, 2026
Result Shipped as reviewable PRs with tests
“Claude code knocked the whole thing out in 8 hours.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
They had Claude itself propose a long list of refactor suggestions for smaller files, smaller functions and more DRY code, narrowed that down to about 8 or 10 items, and had it open a Jira tracking issue with small, tractable subtasks before knocking them out one at a time as reviewable pull requests with test coverage.
How it went
A coworker estimated the manual work at two weeks, and Claude and ChatGPT both estimated 6 to 8 weeks, which the writer calls a wild overestimate. Claude Code finished the whole refactor in 8 hours.
Try it yourself with Claude Code
Ask [your coding agent] to review your codebase and propose a prioritized list of refactor suggestions (smaller files, smaller functions, removing duplication). Narrow the list down with it, have it open tracked subtasks (e.g. in Jira or GitHub Issues) for each one, then have it work through them one at a time as small, reviewable pull requests with test coverage.
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.
Markdown files should just open, so they asked Claude Code for a viewer. It opens instantly: faster, they say, than any other macOS app, and faster than Bitwarden's Chrome extension shows its fill menu.
Migrating a password reset flow, Claude Code and Opus produced code on par with a mid level developer. It needed close supervision throughout, and cost roughly 2 months of Pro subscription for about half a day's work.
A URL shortener side project ran on AWS. Claude Code wrote the GitHub Actions workflows for the move and fixed each failure as it came up. The writer reports zero downtime.
A 7-app monorepo needed an 8 GB memory setting and 25 seconds to typecheck. Claude Code made the changes for the move to oxlint, oxfmt and tsgo, and the team validated each step.
Turning plan files into Claude Code workflows took 5-6 hours each. A script that converts them deterministically, and flags what can move out of the LLM, cut that to 20-30 minutes at about 20% of the tokens.
An inherited app on Azure, an error, and a hunt that could easily take 1-2 days by hand. With CLI access to Azure and the repo, Claude Code ran the config and network checks and found the root cause in about 45 minutes.