Skip to content

notque/vexjoy-agent / skills/analysis/data

Data analysis, reference enrichment, and data engineering: pipelines and warehouses, server database design and tuning, SQLite with Peewee.

references/data/error-catalog.md

View on GitHub
# Data Engineering Error Catalog

## DAG Dependency Deadlock
**Cause**: Circular dependencies between pipeline tasks, or upstream tasks that never complete, blocking the entire DAG.
**Solution**: Map the dependency graph explicitly. Break cycles with staging tables or intermediate datasets. Use Airflow's `ExternalTaskSensor` with timeout for cross-DAG dependencies.

## Late-Arriving Data
**Cause**: Events arrive after the processing window closes (common with mobile apps, IoT, distributed systems).
**Solution**: Implement late-arrival handling: add a reprocessing window (e.g., re-run last 3 days daily), use watermarking in streaming, or design a lambda architecture with batch correction layer.

## Schema Evolution Breakage
**Cause**: Source system schema changes without notice -- columns renamed, types changed, new fields added.
**Solution**: Implement data contracts between producer and consumer. Use schema registry for streaming (Confluent Schema Registry). Add schema validation as the first step in every extraction pipeline. Alert on schema drift.

## SCD Type Mismatch
**Cause**: Using SCD Type 1 (overwrite) when historical tracking is needed, or Type 2 (versioned rows) when only current state matters (adding unnecessary complexity).
**Solution**: Analyze reporting requirements before choosing. Type 1 for current-only attributes (e.g., customer email). Type 2 for historically significant attributes (e.g., customer segment, address for regional analysis). Document the choice and rationale per dimension.

## Duplicate Records After Re-run
**Cause**: Pipeline uses INSERT instead of MERGE/upsert, or lacks deduplication logic.
**Solution**: Use MERGE statements, partition overwrite (replace entire partition on re-run), or deduplication with ROW_NUMBER() windowed by natural key ordered by load timestamp. Every pipeline must produce identical results regardless of how many times it runs.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall