
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 oth
- Scripts
- None
- Platforms
- Claude Code, Codex, Cursor
- GitHub stars
- 41.3K
- Last commit
- 1 day ago
- License
- MIT
- Listing updated
- today
When your agent uses it
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).
From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.
What it can access
From a static check of its 1 file (6 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.
Install
Copy the skill folder to ~/.claude/skills/sql-object-impact-analysis to use it in all your projects:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/sql-object-impact-analysis &&
cp -R "$tmp/skills/sql-object-impact-analysis" ~/.claude/skills/sql-object-impact-analysis &&
rm -rf "$tmp"For one project only, put the folder in .claude/skills/sql-object-impact-analysis inside it instead.
Copy the skill folder to ~/.agents/skills/sql-object-impact-analysis to use it in every repository:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/sql-object-impact-analysis &&
cp -R "$tmp/skills/sql-object-impact-analysis" ~/.agents/skills/sql-object-impact-analysis &&
rm -rf "$tmp"For one repository only, put the folder in .agents/skills/sql-object-impact-analysis inside it instead.
Copy the skill folder to ~/.cursor/skills/sql-object-impact-analysis to use it in every project:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/sql-object-impact-analysis &&
cp -R "$tmp/skills/sql-object-impact-analysis" ~/.cursor/skills/sql-object-impact-analysis &&
rm -rf "$tmp"For one project only, put the folder in .cursor/skills/sql-object-impact-analysis inside it instead.
Run in a terminal (add --scope workspace to install it for the current workspace only):
gemini skills install https://github.com/github/awesome-copilot.git --path skills/sql-object-impact-analysisOr copy the folder to ~/.gemini/skills/sql-object-impact-analysis yourself.
For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/sql-object-impact-analysis:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/sql-object-impact-analysis &&
cp -R "$tmp/skills/sql-object-impact-analysis" ~/.copilot/skills/sql-object-impact-analysis &&
rm -rf "$tmp"For one project only, put the folder in .github/skills/sql-object-impact-analysis inside it instead.
Get the folder:
git clone --depth 1 https://github.com/github/awesome-copilot.gitThen copy awesome-copilot/skills/sql-object-impact-analysis into your agent's skills folder as sql-object-impact-analysis. Agents that support SKILL.md read one folder per skill.
SQL object impact analysis FAQ
How do I install SQL object impact analysis in Claude Code?
Copy the skill folder from GitHub to ~/.claude/skills/sql-object-impact-analysis to use it in all your projects, or to .claude/skills/sql-object-impact-analysis in one project.
Does SQL object impact analysis run scripts?
No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.
Which AI agents can use SQL object impact analysis?
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.
What are the best alternatives to SQL object impact analysis?
The closest alternatives to SQL object impact analysis are Snowflake semanticview, Migrating oracle to postgres stored procedures, Postgresql optimization, Bigquery pipeline audit and Supabase rls policies.
More from github/awesome-copilot

Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo
- Open source
- 41.3K GitHub stars
- Cloud and infrastructure


Cross-references C# Web API controllers/DTOs against their TypeScript/JavaScript consumers (React, Angular, Vue, Svelte, Node.js, or hand-wr
- Open source
- 41.3K GitHub stars

Instrument a webapp to send useful telemetry data to Azure App Insights
- Open source
- 41.3K GitHub stars

Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.
- Open source
- 41.3K GitHub stars

Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.
- Open source
- 41.3K GitHub stars
Alternatives to SQL object impact analysis

Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow)
- Open source
- 41.3K GitHub stars
- Databases

Migrates Oracle PL/SQL stored procedures to PostgreSQL PL/pgSQL
- Open source
- 41.3K GitHub stars
- Databases

PostgreSQL-specific development assistant focusing on unique PostgreSQL features, advanced data types, and PostgreSQL-exclusive capabilities
- Open source
- 41.3K GitHub stars
- Databases

Audits Python + BigQuery pipelines for cost safety, idempotency, and production readiness
- Open source
- 41.3K GitHub stars
- Databases

Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows
- Open source
- 41.3K GitHub stars
- Databases

Use when: comparing SQL Server tables across instances, data migration validation, ETL verification, row mismatch detection, schema drift, r
- Open source
- 41.3K GitHub stars
- Databases
