Find deprecated usage first
Map the blast radius before starting a migration.
Official basis Refactor step one — locate the deprecated usage, then plan the change. docs ↗
The prompt
Find all usages of <deprecated API or pattern> across the codebase and list them with file paths. Then propose a refactor plan in small, testable steps — don't change anything yet.Why it works
The documented refactor workflow starts with discovery, not edits. Seeing every call site up front lets you scope the change and catch the tricky ones before touching a line.
Fill in
<deprecated API or pattern>— what you’re migrating away from.
Follow-ups
- “Good plan — do the first 3 files, run the tests, then pause.”