From ad-migration
Use when scoping a single table, view, or materialized view for migration and the next step depends on identifying its writer, SQL structure, or dependency call tree from catalog-backed DDL context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ad-migration:analyzing-tableThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scope one table, view, or materialized view from catalog-backed DDL context.
Scope one table, view, or materialized view from catalog-backed DDL context.
Use this skill when:
/scope depends on catalog-backed scoping, not ad-hoc inspectionDo not use this skill when:
$ARGUMENTS is the fully-qualified name (e.g. silver.DimCustomer, silver.vw_CustomerSales). Ask the user if missing.
/scope codes from ../../lib/shared/scope_error_codes.md.warnings or errors must include code, severity, and message.scoping and statements as non-authoritative on reruns. Recompute and overwrite..staging/ under the active project root only. Do not use /tmp.status in persisted scoping payloads.Check stage readiness:
uv run --project "${CLAUDE_PLUGIN_ROOT}/packages/ad-migration-internal" migrate-util ready scope --object <fqn>
If ready is false, report the failing check's code and reason to the user and stop.
Do not run discovery, context, or write commands after a failed readiness check.
Check whether catalog/views/<fqn>.json exists:
| Object | Normal path | Open reference when | Persisted outcome |
|---|---|---|---|
| table | run references/table-pipeline.md | per-candidate procedure analysis: references/procedure-analysis.md; non-trivial writer selection: references/table-writer-resolution.md | selected_writer plus rationale and candidate context |
| view or MV | run references/view-pipeline.md | manual SQL feature inspection needs dialect help: references/statement-classification.md | sql_elements, call_tree, logic_summary, rationale |
Read references/table-pipeline.md and execute it.
Use references/procedure-analysis.md for each candidate procedure.
Use references/table-writer-resolution.md only when writer selection is not trivial.
Read references/view-pipeline.md and execute it.
Use references/statement-classification.md only when manual SQL feature inspection needs dialect-specific help.
Use references/error-handling.md for command exits and reference-level failures.
npx claudepluginhub accelerate-data/vibedata-official --plugin ad-migrationParses database migration scripts and assesses lock contention, downtime risk, rollback strategy, and deployment safety for PostgreSQL and MySQL.
Connects to dlt pipelines, profiles tables, scans schemas, plans charts with ibis and altair, and outputs analysis_plan.md artifacts for data exploration and analysis.
Reviews SQL queries for data analysis: joins, filters, aggregation, metric definitions, and validation. Use when writing or auditing analytical SQL.