{
 "schema_version": 1,
 "generated": "2026-10-26",
 "id": "mikeparcewski-wicked-studio--map-blast-radius-before-change",
 "repo": "mikeparcewski/wicked-studio",
 "repo_url": "https://github.com/mikeparcewski/wicked-studio",
 "repo_slug": "mikeparcewski-wicked-studio",
 "title": "Map a symbol's blast radius before changing code",
 "page_title": "How to map a symbol's blast radius before changing code with Wicked Studio",
 "summary": "Onboard a repo, then check what a change to one symbol would touch.",
 "who": "A developer about to refactor shared code who wants to see its callers and risky hotspots first.",
 "problem": "Changing a widely used symbol without seeing its callers can break parts of the codebase nobody checked.",
 "outcome": "You have a list of affected code and hotspots to review before you start an agent run on the change.",
 "steps": [
  "Run `npx wicked-crew serve` and 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."
 ],
 "agent_prompt": "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.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "The code graph is built by studio after onboarding, so results only cover the repo state at the time it was built.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "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"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.8,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/map-blast-radius-before-change/",
 "md": "https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/map-blast-radius-before-change/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/mikeparcewski-wicked-studio--map-blast-radius-before-change.json",
 "api_version": "v1"
}