Sql Object Impact Analysis
Before modifying a table, column, stored procedure, view, or trigger in a legacy codebase, trace every place that references it — across other SQL objects (procs, views, triggers) AND application code (C#, Angular/TypeScript, JS, or any language in the repo) — and produce a structured blast-radius report so you know what breaks before you change it. Use when the user asks 'what uses this column/table/procedure', 'is it safe to change X', 'what depends on this', 'impact of renaming/dropping X', or before any schema/proc modification in an unfamiliar or legacy codebase. Not for privacy/PII exposure analysis (see data-breach-blast-radius) or query performance tuning (see sql-optimization).
Awesome GitHub Copilotv10 stars · 0 forks · 0 makes≈1.2K tokens
Scores by version
No eval runs reported yet. Incantory never runs prompts: owners report results from their own CI.
Datasets
No datasets.