Delete safely
Find blockers and orphans before removing a file or symbol.
Ask what would break — and what would be left dead — if a target went away.
prism safe-delete src/legacy/adapter.ts
prism blast src/legacy/adapter.ts --deletesafe-delete never deletes anything. It only reports.
What you get back
| Result | Meaning |
|---|---|
| Blockers | Things that would fail to resolve if the target disappeared |
| Orphans | Files left unreachable because only this target reached them |
| Delete-oriented blast | Same graph as edit blast, weighted toward breakage |
Orphans are the useful half — deleting one module often leaves three dead.
When this is wrong
- Missing edges (dynamic imports, DI) mean false "safe" answers — still review.
- Renames are a different question: use
prism rename/rename_impact. - Public package exports may break consumers outside this repo; breaking-change hints flag that case, they do not prove safety.