New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

SQL Object Impact Analysis

by github in github/awesome-copilot

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…

OfficialMITAuto-check passedDatabases

Install SQL Object Impact Analysis

skills CLI
$ npx skills add github/awesome-copilot --skill sql-object-impact-analysis -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot sql-object-impact-analysis --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sql-object-impact-analysis .claude/skills/sql-object-impact-analysis && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sql-object-impact-analysis
GitHub stars
40k
Token cost
~1.4k tokens
SKILL.md length
715 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 5 steps: Confirm the target object and its exact… → Search the SQL layer first → Search the application layer → …
  • In a legacy codebase
  • SKILL.md covers When to use this, Process, Output Format and Guidelines
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

SQL Object Impact Analysis is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. 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…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases, covering SQL. It works with SQL, Angular, C# and TypeScript. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • In a legacy codebase
  • Trace every place that references it — across other SQL objects (procs
  • Triggers) AND application code (C
  • Angular/TypeScript

Example prompts

  • “what uses this column/table/procedure”
  • “is it safe to change X”
  • “what depends on this”
  • “/sql-object-impact-analysis”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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…
  2. Search the SQL layer first
  3. Search the application layer
  4. Classify each finding by confidence
  5. Produce the report (see Output Format below).

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

SQL Object Impact Analysis loads about 1.4k tokens when it runs. Until then it costs about 181 tokens; SKILL.md has 715 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~181
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 715 words, ~1,422 tokens.

Download SKILL.mdSave it as .claude/skills/sql-object-impact-analysis/SKILL.md (or your agent's skills folder).
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).

Show full SKILL.md (271 more words)Show less

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.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/sql-object-impact-analysis of github/awesome-copilot.

Open the folder on GitHubat commit 727ff2e

Compare with similar skills

SQL Object Impact Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

SQL Object Impact Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
SQL Object Impact Analysis this skillgithub/awesome-copilot40k—~1.4kAutomated safety check: PassMIT
NpgsqlrestNpgsqlRest/NpgsqlRest132—~7kAutomated safety check: NotesMIT
Faasjs Pgfaasjs/faasjs121—~718Automated safety check: PassMIT
Drizzle Ormgrowupanand/ConvoForm1011 repos~2.7kAutomated safety check: PassApache-2.0
Golem Add Ignite TSgolemcloud/golem1.5k—~482Automated safety check: PassCustom licence
Golem Add Mysql TSgolemcloud/golem1.5k—~441Automated safety check: PassCustom licence

Similar skills

  • Npgsqlrest

    NpgsqlRest/NpgsqlRest

    Build and modify REST APIs with NpgsqlRest — exposing PostgreSQL as HTTP endpoints from two sources (database functions/procedures/tables/views, and plain .sql files), driven by SQL comment…

    132 GitHub stars~7k tokensUpdated 4 days ago
    DatabasesAuto-check: notes

  • Faasjs Pg

    faasjs/faasjs

    A skill your agent uses when working with @faasjs/pg or PostgreSQL in FaasJS: Tables declaration merging, QueryBuilder, select aliases, parameterized sql expressions, raw SQL, numeric/decimal/bigint…

    121 GitHub stars~718 tokensUpdated 1 mo ago
    DatabasesAuto-check passed

  • Drizzle Orm

    growupanand/ConvoForm

    Type-safe SQL ORM for TypeScript with zero runtime overhead. An agent skill from growupanand/ConvoForm.

    101 GitHub starsUsed in 1 repo~2.7k tokens
    DatabasesAuto-check passed

  • Golem Add Ignite TS

    golemcloud/golem

    Using golem:rdbms/ignite2 from a TypeScript Golem agent. An agent skill from golemcloud/golem.

    1.5k GitHub stars~482 tokensUpdated today
    DatabasesAuto-check passed

  • Golem Add Mysql TS

    golemcloud/golem

    Using golem:rdbms/mysql from a TypeScript Golem agent. An agent skill from golemcloud/golem.

    1.5k GitHub stars~441 tokensUpdated today
    DatabasesAuto-check passed

  • Golem Add Postgres TS

    golemcloud/golem

    Using golem:rdbms/postgres from a TypeScript Golem agent. An agent skill from golemcloud/golem.

    1.5k GitHub stars~519 tokensUpdated today
    DatabasesAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about SQL Object Impact Analysis

What does SQL Object Impact Analysis do?

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…. SQL Object Impact Analysis is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. 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.

When should I use SQL Object Impact Analysis?

SQL Object Impact Analysis fits situations like: in a legacy codebase; trace every place that references it — across other SQL objects (procs; triggers) AND application code (C; angular/TypeScript.

How do I install SQL Object Impact Analysis in Claude Code?

Run `npx skills add github/awesome-copilot --skill sql-object-impact-analysis -a claude-code`. Or copy the skill folder (skills/sql-object-impact-analysis in github/awesome-copilot) into .claude/skills/sql-object-impact-analysis in your project. Claude Code loads it when a task matches its description.

How do I install SQL Object Impact Analysis in Codex?

Run `npx skills add github/awesome-copilot --skill sql-object-impact-analysis -a codex`. Or copy the skill folder (skills/sql-object-impact-analysis in github/awesome-copilot) into .agents/skills/sql-object-impact-analysis in your project. Codex loads it when a task matches its description.

Can I use SQL Object Impact Analysis in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill sql-object-impact-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sql-object-impact-analysis, .gemini/skills/sql-object-impact-analysis, .github/skills/sql-object-impact-analysis and .opencode/skills/sql-object-impact-analysis in your project.

What does SQL Object Impact Analysis need to run?

SKILL.md names no scripts, command-line tools or credentials: SQL Object Impact Analysis is instructions for the agent only.

Does SQL Object Impact Analysis access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is SQL Object Impact Analysis safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does SQL Object Impact Analysis use?

SQL Object Impact Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does SQL Object Impact Analysis use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to SQL Object Impact Analysis?

Skills that share tags, products or a category with SQL Object Impact Analysis: Npgsqlrest (NpgsqlRest/NpgsqlRest, 132 stars), Faasjs Pg (faasjs/faasjs, 121 stars), Drizzle Orm (growupanand/ConvoForm, 101 stars) and Golem Add Ignite TS (golemcloud/golem, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SQL Object Impact Analysis?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.