Rename a core type across a monorepo
A Builder.io engineer handed Claude Code a TypeScript type rename across a monorepo and let it finish in one session while they context-switched.
- Agent or tool
- Claude Code
- Topic
- Software Development
- Reported on
- Blog
- Added
- 2026-10-15
Why it matters
Coding agents are moving from autocomplete to doing whole tasks: reading a codebase, making a plan and changing many files. This case is a concrete example of where that works in practice. It is one of 106 sightings filed under Software Development on Agent Sightings (number 93 by interest), and one of 164 involving Claude Code.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Claude Code or any similar agent and adjust the details to your situation.
Rename type <OldName> to <NewName> across this monorepo. Update imports, tests and docs. Run the test suite after each major package and summarize remaining references.
The prompt breaks down into 3 steps you can check as the agent works:
- Rename type <OldName> to <NewName> across this monorepo.
- Update imports, tests and docs.
- Run the test suite after each major package and summarize remaining references.
Tip: Work on a fresh branch, ask for a plan before edits, and review the diff and test results before merging.
Source
Read the original first-hand account on Blog: https://www.builder.io/blog/cursor-vs-claude-code. Our summary is a paraphrase; details are in the source.