dataform-bigquery

Generates and validates Dataform SQLX pipeline code for BigQuery ELT workflows.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/SmileAfterBurn/pani-dumka-ai --skill dataform-bigquery-smileafterburn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dataform-bigquery
Source: https://github.com/SmileAfterBurn/pani-dumka-ai/tree/main/.gemini/skills/dataform-bigquery
Command: npx skills add https://github.com/SmileAfterBurn/pani-dumka-ai --skill dataform-bigquery-smileafterburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing correct Dataform pipelines for BigQuery requires deep knowledge of SQLX syntax, incremental table semantics, source declarations, and GCS ingestion patterns. This Skill guides an AI agent through the full lifecycle of creating, modifying, compiling, and validating Dataform projects so pipelines are correct before execution. ## Core Features & Use Cases - Pipeline Generation & Modification: Creates SQLX actions, source declarations, and incremental tables following Dataform best practices, including BigLake Iceberg 4-part naming workarounds. - Automatic Data Cleaning & SQL Optimization: Applies mandatory data-cleaning protocols and BigQuery SQL optimizations to every transformation, with summary sections in each response. - Validation Workflow: Compiles projects with dataform compile, validates with dataform run --dry-run or bq query --dry_run, and never executes a real run without explicit user confirmation. - Use Case: You need to ingest CSV files from a GCS bucket into an existing BigQuery table. The Skill initializes or locates the Dataform repository, creates an external table via an operations file, builds an incremental SQLX action with schema-aligned columns, and validates the whole DAG before you approve execution. ## Quick Start Create a Dataform pipeline that loads CSV files from my GCS bucket into BigQuery and validate it with a dry run.

Frequently Asked Questions about dataform-bigquery

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

FAQPage Schema
How do I create a Dataform pipeline for BigQuery?▼

Initialize a repository with `dataform init`, declare BigQuery sources in declaration SQLX files, then define table or incremental actions that reference sources via `${ref()}`. Validate everything with `dataform compile` and `dataform run --dry-run` before any real execution.

How to append data to an existing BigQuery table with Dataform?▼

Use `type: "incremental"` with the existing table name as the action name, and write only a SELECT statement in the body. Dataform auto-generates the INSERT, so never use `type: "operations"` or manual INSERT statements for append operations.

Does Dataform support BigLake Iceberg tables with 4-part naming?▼

Dataform natively supports only 3-part naming, but you can concatenate the catalog and namespace into the declaration's schema field, such as `schema: "my_catalog.my_namespace"`. Views cannot be created directly from BigLake sources using 4-part names.

Why does dataform run --dry-run fail with table not found errors?▼

This happens when upstream tables defined in the project have not been materialized in BigQuery yet. These specific errors can be ignored, but SQL syntax errors, permission errors, or references to tables outside the project must be fixed.

How do I ingest CSV files from GCS into BigQuery using Dataform?▼

Create an external table in a SQLX operations file pointing at the GCS URI, using STRING for all columns with `allow_jagged_rows`, `allow_quoted_newlines`, and `ignore_unknown_values` set to true. Then build incremental or table actions on top of it.