skippr run

This is where the full pipeline runs. One command kicks off the public flow described in the docs: discover the source, sync raw data, draft dbt assets, and validate the result against your destination.

Usage

skippr run [--log <level>]

By default you get a live terminal UI showing phases, tasks, and progress in real time. For CI or scripted environments, use --log for structured output.

After a run, you can send feedback for the most recent project run with skippr feedback. That feedback is sent to the Skippr support platform to help engineers debug issues and support your workflows.

Flags

Flag	Description
--log info	Structured logs to stdout (great for CI)
--log debug	Debug-level logs
--log trace	Maximum verbosity

Pipeline phases

The terminal UI is more detailed than the high-level docs model:

Public step	Terminal phases	What happens
Discover	Discover	Read source schemas and determine the destination shape
Sync	Sync, Verify	Load bronze data and confirm the destination objects are ready
Model	Plan, Author	Draft dbt models, naming, and casts
Validate	Validate, Review	Run dbt and check the generated output

Re-runs are incremental -- only new and changed data is synced, and existing models are preserved.

If a run fails, start with Troubleshooting and the source or destination connector guide for environment-specific fixes.

Example

source .venv/bin/activate
skippr run

With structured logging:

skippr run --log info

Then leave feedback on the most recent run:

Leave positive feedback after a successful run:

skippr feedback --good --comment "all the data is synced and the auto-generated models are already providing valuable insight"

Flag a bad run with a comment:

skippr feedback --bad --comment "synced data, schemas look great, but stalled in review and never finished"

Exit codes

Code	Meaning
0	Pipeline completed successfully
1	Pipeline failed (check logs)
130	Interrupted (Ctrl+C)