菜单
Accountability for identifying deprecated Lightdash API usage in the provider by comparing code patterns against the official OpenAPI specification. Use when tasked to audit the codebase for technical debt or outdated API dependencies.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guide the execution of Lightdash Terraform provider acceptance tests, ensuring correct environment setup and targeted test execution.
Run formatting, linters, unit tests, and build checks, then fix violations.
Implement verified Lightdash API clients with documentation research and live schema verification.
Research and investigate Lightdash API endpoints to understand request/response schemas and behavior.
Implement Terraform Resources and Data Sources in `internal/provider` with comprehensive testing.
Comprehensive security review of the Terraform provider codebase using gosec, trunk, osv-scanner, and trivy.
| name | investigate-deprecated-apis |
| description | Accountability for identifying deprecated Lightdash API usage in the provider by comparing code patterns against the official OpenAPI specification. Use when tasked to audit the codebase for technical debt or outdated API dependencies. |
To provide a systematic methodology for identifying technical debt related to Lightdash API deprecations. This skill defines the "what" and "why" of the audit process, ensuring the provider remains resilient against breaking API changes.
An endpoint is considered a candidate for migration if:
deprecated: true in the OpenAPI specification./api/v1/ and a corresponding functional equivalent exists in /api/v2/.Identify potential API usage by searching internal/lightdash/api/ for versioned path patterns.
grep or rg to find "/api/v1/ or "/api/v2/.Compare identified patterns against the official Lightdash OpenAPI source of truth.
https://raw.githubusercontent.com/lightdash/lightdash/refs/heads/main/packages/backend/src/generated/swagger.jsondeprecated flag.For each deprecated endpoint, determine: