Expert documentation generation for hist-union workflows. Documents historical and incremental table combination strategies, schema validation, time-based partitioning, and backfill processes. Use when documenting hist-union layers.
51
55%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./aps-doc-skills/hist-union/SKILL.mdSpecialized skill for generating comprehensive documentation for hist-union workflows that combine historical and incremental table data.
Use this skill when:
Example requests:
"Document the hist-union workflow for events table"
"Create documentation for historical data combination"
"Document the backfill process for customer data"
"Generate hist-union documentation following this template: [Confluence URL]"WITHOUT codebase access = NO documentation. Period.
If no codebase access provided:
I cannot create technical documentation without codebase access.
Required:
- Directory path to hist-union workflows
- Access to .dig, .sql, .yml files
Without access, I cannot extract real table names, union logic, or configurations.
Provide path: "Code is in /path/to/histunion/"Before proceeding:
Documentation MUST contain:
NO generic placeholders. Only real, extracted data.
Follow this EXACT structure (analyzed from production examples):
# Hist_Union Project Documentation
## Overview
{Brief description of hist-union purpose}
**Key Features:**
- {Feature from actual workflow}
- {Feature from actual workflow}
---
## Architecture
### Project Structure
{Actual directory tree from codebase}
### Configuration
**Databases:**
{Table with database names and purposes}
**Watermark Table:**
{inc_log table structure and purpose}
---
## Processing Patterns
### Pattern 1: Incremental Load (Watermark-Based)
{Explain watermark tracking using inc_log}
**SQL Pattern:**
{Real SQL showing UNION ALL with watermark logic}
### Pattern 2: Full Load (Complete Reload)
{Explain full reload pattern}
**SQL Pattern:**
{Real SQL showing full reload}
---
## Watermark Management
**inc_log Table:**
{Schema and purpose}
**Watermark Update Logic:**
{Explain how watermarks are updated}
---
## Main Workflow Configuration
**Workflow File:** {hist_union_runner.dig}
**Key Features:**
- {Feature from actual .dig file}
- {Feature from actual .dig file}
**Parallel Execution:**
{Explain _parallel settings}
---
## SQL Query Examples
### Example 1: Incremental Load Pattern
{Real SQL from codebase}
### Example 2: Full Load Pattern
{Real SQL from codebase}
### Example 3: Complex Schema
{Real SQL from codebase if applicable}
---
## Tables Processed
{Table organized by data source listing all tables}
---
## Execution Flow
{Step-by-step workflow execution}
**Execution Commands:**
{Real commands from codebase}
---
## Best Practices
{List from actual implementation}
---
## Troubleshooting
**Common Issues:**
{Real issues and solutions}
**Monitoring Queries:**
{Real SQL for checking status}
---
## Maintenance
{Maintenance tasks and schedules}
---
## Summary
{Brief recap of capabilities}Template Usage Notes:
This skill generates production-ready hist-union documentation by:
Key capability: Transforms hist-union codebase into professional Confluence documentation with all processing patterns documented.
1a0845f
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.