I built a tool that shows you which files break before you push

I changed one struct field last week. Added blast_radius_weight: f64 to a shared type in models.rs . Saved the file. The sidebar turned red. 417 files affected. Three hops deep. Half the backend. Every integration test. The sync layer, the graph analyzer, the encryption pipeline — all downstream from that one struct. I hadn't pushed. I hadn't left the editor. But I already knew the blast radius. Without this, I'd have found out in CI. Twenty minutes later. What it does I built CodeLayers — it parses your code with tree-sitter, builds a dependency graph, and shows you exactly what's affected when you change something. Two ways to use it: 1. VS Code / Cursor extension Save a file and the blast radius appears instantly: Sidebar tree — every affected file, organized by distance. Red = your change. Orange = direct importers. Yellow, green, blue = further out. File explorer badges — ~1 , ~2 , ~3 on affected files so you see it without opening anything. CodeLens — caller counts above function