sql-authoring

Estrelas0

Forks0

Atualizado10 de junho de 2026 às 12:49

Write and review complex SQL across dialects. Use for CTEs, windows, pivots, temporal joins, recursive queries, MERGE/upsert, SCD logic, dialect translation, query optimization, and SQL anti-pattern detection.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

datacoolie

datacoolie/dekit

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	sql-authoring
description	Write and review complex SQL across dialects. Use for CTEs, windows, pivots, temporal joins, recursive queries, MERGE/upsert, SCD logic, dialect translation, query optimization, and SQL anti-pattern detection.

SQL Authoring

Use this skill for SQL correctness, readability, and performance decisions.

Rules

State the target dialect before relying on syntax.
Prefer clear CTE pipelines over deeply nested subqueries.
Name each CTE by intent, not implementation detail.
Use window functions for dedup, ranking, lag/lead, and running calculations.
Make null behavior explicit in joins, filters, and metrics.
Use MERGE/upsert for idempotent incremental writes when supported.
Validate join cardinality before trusting row counts.

Review Checklist

Does every join have an intentional key and expected cardinality?
Are filters applied at the right layer and before expensive joins where possible?
Are implicit casts avoided?
Are partition/index/filter columns used in predicates?
Are aggregations at the intended grain?
Are date/time zones and inclusive/exclusive ranges explicit?
Are duplicates handled deterministically?

Anti-Patterns

SELECT * in production models.
Correlated subqueries at scale when a join/window is clearer.
DISTINCT used to hide join fan-out.
Metrics with hidden filters or mixed grains.
NOT IN with nullable subquery values.
Non-deterministic dedup without ordering.

Verification

Before reporting SQL done:

Compile or dry-run the query where possible.
Test with empty, single-row, duplicate, and null-heavy inputs.
Compare row count and key uniqueness at each major CTE.
Inspect explain plan for expensive scans or missing pruning.
Reconcile critical metrics to source or prior layer.

Mais deste repositório

mesmo repositório

wiki

datacoolie/dekit

Build and maintain an internal technical LLM wiki when the user requests wiki work or a verified major or architectural change qualifies for automatic wiki review. Use for project memory, architecture notes, contracts, runbooks, decisions, glossary, incremental ingest, delta status, and wiki health. Do not use merely because a routine task or plan completed.

2026-07-180

brainstorm

datacoolie/dekit

Explore ambiguous ideas and solution directions before evidence-backed research or implementation planning. Use for ideation, framing, assumption checks, option generation, product or architecture trade-offs, and deciding whether research or a plan is needed.

2026-07-030

research

datacoolie/dekit

Research technical options with source-backed recommendations. Use for technology evaluation, architecture trade-offs, library/framework choices, best practices, scalability, security, maintainability, or when current external facts matter.

2026-07-030

plan

datacoolie/dekit

Create implementation plans, architecture decisions, and phased roadmaps. Use for Standard or Complex changes, new pipelines, schema changes, migrations, multi-file features, technology choices, or when acceptance criteria and verification strategy are unclear.

2026-06-170

code-review

datacoolie/dekit

Review code and data pipeline changes for correctness, security, performance, maintainability, contract breaks, and missing verification. Use before merge, after implementation, for PRs, commits, pending diffs, or codebase risk scans.

2026-06-100

data-ingestion

datacoolie/dekit

Design data ingestion into landing/bronze layers. Use for source onboarding, transfer pattern selection, full/incremental/CDC scope, change detection, landing zones, schema drift, idempotent file or batch processing, and ingestion quality gates.

2026-06-100

name	sql-authoring
description	Write and review complex SQL across dialects. Use for CTEs, windows, pivots, temporal joins, recursive queries, MERGE/upsert, SCD logic, dialect translation, query optimization, and SQL anti-pattern detection.

SQL Authoring

Use this skill for SQL correctness, readability, and performance decisions.

Rules

State the target dialect before relying on syntax.
Prefer clear CTE pipelines over deeply nested subqueries.
Name each CTE by intent, not implementation detail.
Use window functions for dedup, ranking, lag/lead, and running calculations.
Make null behavior explicit in joins, filters, and metrics.
Use MERGE/upsert for idempotent incremental writes when supported.
Validate join cardinality before trusting row counts.

Review Checklist

Does every join have an intentional key and expected cardinality?
Are filters applied at the right layer and before expensive joins where possible?
Are implicit casts avoided?
Are partition/index/filter columns used in predicates?
Are aggregations at the intended grain?
Are date/time zones and inclusive/exclusive ranges explicit?
Are duplicates handled deterministically?

Anti-Patterns

SELECT * in production models.
Correlated subqueries at scale when a join/window is clearer.
DISTINCT used to hide join fan-out.
Metrics with hidden filters or mixed grains.
NOT IN with nullable subquery values.
Non-deterministic dedup without ordering.

Verification

Before reporting SQL done:

Compile or dry-run the query where possible.
Test with empty, single-row, duplicate, and null-heavy inputs.
Compare row count and key uniqueness at each major CTE.
Inspect explain plan for expensive scans or missing pruning.
Reconcile critical metrics to source or prior layer.