Who it is forA developer about to refactor shared code who wants to see its callers and risky hotspots first.
The problemChanging a widely used symbol without seeing its callers can break parts of the codebase nobody checked.
The outcomeYou have a list of affected code and hotspots to review before you start an agent run on the change.
What you need first
- Node.js 22 or newer and npm 10 or newer
- A container runtime for jobs: Rancher Desktop, Docker, Podman, Colima or OrbStack
- At least one coding-agent CLI you already use, such as Claude Code or Codex
- A modern browser such as Chrome, Edge, Firefox or Safari on macOS
Steps
- Run
npx wicked-crew serveand open the studio URL it prints. - Register your repo by local path or by cloning its URL, then let studio build the code graph.
- Open the graph view and search for the symbol you plan to change.
- Check its blast radius and the hotspots list, then note the files to review.
- Start a run on the change only after you have reviewed those files.
Prompt for your agent
Using wicked-studio, onboard the repo at <repo path> and open the blast radius for the symbol <symbol name>. Expected output: a list of affected files and the hotspots in the same area. Verify that every file in the list appears in the graph view before you start any run.
Caveat. The code graph is built by studio after onboarding, so results only cover the repo state at the time it was built.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for mikeparcewski/wicked-studio and "Map a symbol's blast radius before changing code"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer