Not exactly what you want, but in SSMS you can right-click on a proc in Object Explorer and select 'View Dependencies' to see what depends on the proc (or what the proc depends on).
A more robust solution is to create a Visual Studio database project and to use the 'build' functionality to detect such issues before they get deployed.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.