aps-doc-hist-union

Generate hist-union documentation with SQL examples from codebase configurations.

21|24|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/treasure-data/td-skills --skill aps-doc-hist-union
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aps-doc-hist-union
Source: https://github.com/treasure-data/td-skills/tree/main/aps-doc-skills/hist-union
Command: npx skills add https://github.com/treasure-data/td-skills --skill aps-doc-hist-union

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation for hist-union workflows, including incremental and full load patterns, watermark management, and merge rules.

Core Features & Use Cases

  • Incremental and full load patterns with unions
  • Watermark tracking and backfill considerations
  • SQL examples for union-based transformations

Quick Start

Document the hist-union process with an example workflow.

Frequently Asked Questions about aps-doc-hist-union

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document hist-union SQL workflows for historical table merges?

Hist-union documentation generation extracts union logic, merge strategies, and backfill processes from your .dig, .sql, and .yml configuration files. It produces production-ready documentation with real table names, actual SQL examples, file paths, and line numbers for incremental and full-load patterns.

What's the best way to validate schema consistency across union-based table merges?

The Skill applies schema validation and consistency checks as part of hist-union documentation, ensuring merge rules are correctly implemented across multiple databases. It captures watermark management and backfill considerations in the generated documentation.

Can I use hist-union documentation for incremental backfill workflows?

Yes. Hist-union documentation handles incremental and full-load patterns, watermark tracking, and backfill processes. It documents the merge strategies and SQL union logic required for backfill operations across your database workflows.

How do I extract SQL union examples from my workflow configuration files?

The Skill parses .dig, .sql, and .yml files to derive working SQL examples and union logic directly from your codebase. It documents the actual SQL transformations with real table names and file references for transparency.

Why document merge strategies for historical table workflows?

Documenting merge strategies ensures reproducibility, reduces errors during incremental updates, and clarifies watermark boundaries and backfill logic. Production-ready documentation with working examples prevents inconsistencies across multiple databases.