skippr reset

Delete Skippr-owned state for one configured pipeline. Use this when you want to re-run a pipeline from a clean Skippr state without deleting source data, warehouse data, or schema sink resources.

Usage

skippr [--config <path>] reset --pipeline <name>
skippr [--config <path>] reset --pipeline <name> --yes

What it deletes

reset is pipeline-scoped. For the selected pipeline it deletes:

• Local skipprd runtime state, including offsets, cached metadata, WAL/buffer state, and runtime artifacts under the pipeline data directory.
• Remote skipprd metadata and runtime state under the configured Skippr storage prefix.
• Hosted modeling state for that pipeline, including model threads, control state, plans, dbt project artifacts, and related model run artifacts.

What it does not delete

reset does not delete data managed by your source, destination, schema sink, or warehouse:

• No source connector data is removed.
• No data sink or warehouse schemas/tables are dropped.
• No schema sink resources are deleted.
• No manifest-defined table data prefixes are deleted.

Confirmation

By default, reset prints the exact local directories and storage prefixes it will delete, then asks you to type yes.

Use --yes only for automation:

skippr reset --pipeline mssql-migration --yes

Arguments

Argument	Required	Description
--pipeline <name>	Yes	Pipeline from skippr.yml to reset.
--yes	No	Skip the interactive confirmation prompt.

Example

skippr reset --pipeline mssql-migration
skippr sync --pipeline mssql-migration --once
skippr model --pipeline mssql-migration

This clears Skippr's state for mssql-migration, then syncs and models the pipeline again from the current source and warehouse configuration.