---
title: "SQL Object Impact Analysis: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/github-sql-object-impact-analysis/
description: "Before a schema change, traces every reference to a table, column, stored procedure, view or trigger across both SQL objects and application code, and produces a structured blast-radius report with confidence-classified findings."
---

# SQL Object Impact Analysis: review, setup & limitations · Undominated.ai

> Before a schema change, traces every reference to a table, column, stored procedure, view or trigger across both SQL objects and application code, and produces a structured blast-radius report with confidence-classified findings.

[← Explore all skills](/skills/)

DATABASES / GitHub community

# SQL Object Impact Analysis

Before a schema change, traces every reference to a table, column, stored procedure, view or trigger across both SQL objects and application code, and produces a structured blast-radius report with confidence-classified findings.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/github/awesome-copilot/tree/2dfe04eaeb5faf9c168d78041d660c0123893d85/skills/sql-object-impact-analysis)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 5 linked sources
 Publisher GitHub community
 Licence [MIT ↗](https://github.com/github/awesome-copilot/blob/2dfe04eaeb5faf9c168d78041d660c0123893d85/LICENSE)
 Revision 2dfe04eaeb5f
 [Read what was—and wasn’t—checked ↓](#review)

“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. …”

 [GitHub community · upstream description ↗](https://github.com/github/awesome-copilot/blob/2dfe04eaeb5faf9c168d78041d660c0123893d85/skills/sql-object-impact-analysis/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Classifies every finding as Direct, Indirect or Uncertain and forbids presenting an Uncertain finding as Direct — the report must state the search method used and its limits instead of implying completeness.
- Carries a hard anti-fabrication rule — never invent a file path, proc name or line reference; 'no references found via text search' is an explicit result — and calls out scheduled jobs, external integrations and reporting layers as the dependents that get missed.

### A good fit for

 - A pre-change safety check before renaming or dropping a schema object in a legacy or unfamiliar codebase
- Answering what depends on a column, table or stored procedure, with a risk summary and concrete verification steps
- Identify scheduled jobs and external integrations in a database-object change impact report.

### Weigh up before choosing

 - Static text search cannot resolve every dynamic-SQL construction or reflection-based ORM mapping; the skill says so itself and requires the report to say so.
- No query execution or live catalog introspection — the trace is over source text, not a running database.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - skills/sql-object-impact-analysis/SKILL.md
- LICENSE
- SKILL.md and LICENSE re-read at 2dfe04ea on 2026-10-13 for the downloadable definition; both byte-identical at HEAD 156736fb (git blob SHAs).
- vercel-labs/skills@7407f3893ad4dceab546ac002c3ef806e4000c73:README.md

### Our findings

 - The output format is six fixed parts — target object, direct SQL dependents, application-code dependents grouped by layer, indirect/dynamic references, a risk summary, and suggested verification steps.
- The process searches one layer beyond the data path where reasonable and flags 'further downstream consumers likely exist' when the trail runs cold rather than guessing.
- For codebases too large for one pass, it demands explicit scoping — search one module first — rather than silently producing a partial report as if complete.
- The trace includes scheduled job invocations and foreign-key relationships. It labels direct, indirect and uncertain references separately and stops downstream UI tracing when evidence runs out.

### Not established by this review

 - No impact analysis was run against a real codebase.
- No schema change was made or validated through this skill.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md)

DOCUMENTED COMMAND

 npx skills add github/awesome-copilot/skills/sql-object-impact-analysis Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills add https://github.com/github/awesome-copilot/tree/2dfe04eaeb5faf9c168d78041d660c0123893d85/skills/sql-object-impact-analysis Copy reviewed-revision command ↗ - Install the skill directory; the definition is self-contained with its output format and guidelines inline.
- Choose your AI tools and project or global scope in the installer, then review its permissions before using the skill.
- For manual installation instead, download the complete bundle from https://undominated.ai/resources/skills/github-sql-object-impact-analysis/bundle.zip and extract it into a new directory. It holds SKILL.md unchanged at revision 2dfe04ea, the upstream licence and an attribution file.
- Place the extracted directory in your host's documented skills directory, named sql-object-impact-analysis. Keep SKILL.md and the licence together.

### Before you start

 - Node.js/npm for this installer
- An agent that supports the Agent Skills format
- A codebase containing SQL objects and the application code that references them

### Compatibility

Agent Skills-compatible coding agents · Any SQL database and any application language present in the repository

### Reads SQL and application source; writes a report

 - Read schema files, stored procedures, views and application code
- Write the blast-radius report when authorized
- No database credentials or query execution are required

### Cost model

The instruction package is MIT-licensed; agent usage has its own costs.

THE COMPLETE REVIEWED DEFINITION

## Read it before you reuse it.

Original source bytes, with attribution. Review the host-specific setup notes above.

 Copy definition ↗ [Download definition + licence ↗](/resources/skills/github-sql-object-impact-analysis/bundle.zip)[Raw Markdown ↗](/resources/skills/github-sql-object-impact-analysis/definition.md)
 ---
name: sql-object-impact-analysis
description: "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)."
---

# SQL Object Impact Analysis

You are performing a **pre-change dependency trace** for a database object (table, column, stored procedure, view, function, or trigger) inside a legacy or unfamiliar codebase. The goal is a single, trustworthy answer to: *"If I change this, what else is affected?"*

## When to use this

Trigger when the user:
- Names a specific table, column, stored procedure, view, or trigger and asks what uses it, what depends on it, or whether it's safe to change/rename/drop
- Is about to modify a schema element in a codebase with no ORM, or a mixed legacy stack (raw SQL + stored procs + hand-written data access code)
- Asks for a "blast radius," "impact analysis," or "dependency trace" of a specific DB object

Do not use this for:
- General SQL performance tuning (use `sql-optimization`)
- SQL code quality/security review (use `sql-code-review`)
- Privacy/PII exposure analysis (use `data-breach-blast-radius`)
- Architecture-level documentation of an entire codebase (use `doc-and-modernize`)

## Process

1. **Confirm the target object and its exact name(s).** Ask if ambiguous (e.g., multiple tables with similar names, or the user says "the customer table" without specifying schema). Get the precise identifier before searching.

2. **Search the SQL layer first:**
 - Search all `.sql` files, stored procedure definitions, views, functions, and triggers in the repo/database scripts folder for direct references to the object name
 - For a column: check every proc/view/trigger that selects, inserts, updates, or filters on it
 - For a table: check every proc/view/trigger that references it, plus foreign key relationships to/from other tables
 - For a stored procedure: check every other proc that calls it, and every scheduled job/agent step that invokes it
 - Note indirect references too — dynamic SQL (`EXEC(@sql)`), synonyms, and views built on views

3. **Search the application layer:**
 - Search all application code (C#, Java, JS/TS, Angular, whatever the repo contains) for:
 - Direct SQL strings referencing the object name
 - ORM/data-access-layer method or class names that map to it (e.g., a repository method calling the stored procedure)
 - API endpoint handlers that ultimately call into the affected data path
 - Trace one layer further where reasonable: does a frontend component consume an endpoint that touches this object? Note it, but don't chase every UI consumer exhaustively — flag "further downstream consumers likely exist" if the trail runs cold rather than guessing.

4. **Classify each finding by confidence:**
 - **Direct** — object name found verbatim in code/SQL
 - **Indirect** — reached via a proc call chain, ORM mapping, or dynamic SQL that couldn't be fully resolved statically
 - **Uncertain** — plausible but unverified (e.g., dynamic SQL construction that couldn't be traced to a literal object name)
 - Never present an Uncertain finding as if it were Direct — flag it clearly so the reader knows to verify manually

5. **Produce the report** (see Output Format below).

## Output Format

Always structure the report as:

1. **Target Object** — exact name, type (table/column/proc/view/trigger), and schema
2. **Direct SQL Dependents** — list of procs/views/triggers/functions that reference it directly, grouped by object type
3. **Application Code Dependents** — list of files/classes/methods that reference it, grouped by layer (data access, API/service, frontend), with file paths
4. **Indirect / Dynamic References** — anything found via dynamic SQL, synonyms, or call chains that couldn't be fully resolved — labeled clearly as needing manual verification
5. **Risk Summary** — one paragraph: is this object narrowly used (low risk) or widely fanned-out (high risk)? Call out anything that touches a scheduled job, external integration, or reporting layer specifically, since those often get missed
6. **Suggested Verification Steps** — concrete next actions before making the change (e.g., "run these two procs against staging data first," "check if the ReportingService endpoint at X depends on this column")

## Guidelines

- Never claim a dependency is complete or exhaustive — static text search cannot catch every dynamic SQL construction or reflection-based ORM mapping. State the search method used and its limits explicitly in the report.
- Never fabricate a file path, proc name, or line reference. If you searched and found nothing, say "no references found via text search" — not silence, and not an invented result.
- If the codebase is large enough that a full trace isn't feasible in one pass, say so and propose scoping (e.g., "search only the `Orders` module first") rather than silently producing a partial report as if it were complete.
- Keep the report scannable — this is a pre-change safety check someone will read in a few minutes before making a decision, not a full architecture document.

The download contains SKILL.md . Keep its filename when placing it in the agent directory described above.

By **GitHub community**. [Exact upstream source ↗](https://github.com/github/awesome-copilot/blob/2dfe04eaeb5faf9c168d78041d660c0123893d85/skills/sql-object-impact-analysis/SKILL.md) · [Licence](/resources/skills/github-sql-object-impact-analysis/LICENSE.txt) · [Attribution](/resources/skills/github-sql-object-impact-analysis/ATTRIBUTION.txt)

SHA-256 9cb296c92e45ebdfbdfe2e6452d5e73fc6ef7bc23dd70a1bfbbdfd3d3e3fb393

 Read the applicable licence MIT License

Copyright GitHub, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Skill definition at reviewed revision ↗](https://github.com/github/awesome-copilot/blob/2dfe04eaeb5faf9c168d78041d660c0123893d85/skills/sql-object-impact-analysis/SKILL.md) Checked 2026-10-13 https://github.com/github/awesome-copilot/blob/2dfe04eaeb5faf9c168d78041d660c0123893d85/skills/sql-object-impact-analysis/SKILL.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, compatibility, access
- [Upstream license or licensing declaration ↗](https://github.com/github/awesome-copilot/blob/2dfe04eaeb5faf9c168d78041d660c0123893d85/LICENSE) Checked 2026-10-13 https://github.com/github/awesome-copilot/blob/2dfe04eaeb5faf9c168d78041d660c0123893d85/LICENSE Supports: license
- [Publisher installation and project documentation ↗](https://github.com/github/awesome-copilot/blob/2dfe04eaeb5faf9c168d78041d660c0123893d85/README.md) Checked 2026-10-07 https://github.com/github/awesome-copilot/blob/2dfe04eaeb5faf9c168d78041d660c0123893d85/README.md Supports: install, compatibility, access
- [Skills installer source formats and selective installation ↗](https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md) Checked 2026-10-07 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md Supports: install
- [Pinned continuation review W32 ↗](https://raw.githubusercontent.com/github/awesome-copilot/2dfe04eaeb5faf9c168d78041d660c0123893d85/skills/sql-object-impact-analysis/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/github/awesome-copilot/2dfe04eaeb5faf9c168d78041d660c0123893d85/skills/sql-object-impact-analysis/SKILL.md Supports: review.findings, bestFor, upstreamDescription

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### CockroachDB SQL ↗ Cockroach Labs skill that turns a natural-language request into CockroachDB SQL, applies the relevant rule files with 00-fundamental-principles.md first, and tells the agent to run EXPLAIN on every generated query when a cluster connection is available.](/skills/cockroachlabs-cockroachdb-sql/)[### dbt Documentation Maintenance ↗ Audits descriptions in a dbt manifest and drafts missing model or column documentation in the project’s existing style.](/skills/dbt-labs-maintaining-dbt-documentation/)[### DuckDB read file ↗ DuckDB's read-file skill: one DuckDB CLI command that picks a reader by file extension and returns a file's schema, row count and first 20 rows, for local paths or HTTPS, S3, GCS and Azure URLs.](/skills/duckdb-read-file/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
