skippr init

Create a new project. This is always the first step -- it sets up the config file and tells you exactly what to do next.

Usage

skippr init <project-name>

What it creates

• skippr.yml -- your project config (warehouse, source, and pipeline settings all live here).
• .env.example -- lists the environment variables you'll need.
• project scaffolding required for the runner and generated dbt output.

Arguments

Argument	Required	Description
project-name	Yes	Project identifier. Used as the pipeline name and dbt schema prefix (e.g. my_project_silver).

Example

mkdir my-workspace && cd my-workspace
skippr init mssql-migration

Output:

Initialised project 'mssql-migration' in /Users/me/my-workspace

Next steps:
  skippr connect warehouse snowflake
  skippr connect source mssql
  skippr doctor
  skippr sync --pipeline mssql-migration --once
  skippr model --pipeline mssql-migration

Notes

• Running init in a directory that already has skippr.yml is idempotent. It will print that the project is already initialised and leave the existing files alone.
• Use skippr reset --pipeline <name> if you want to clear Skippr-owned runtime and modeling state for a configured pipeline.
• The project name should be a valid identifier (letters, numbers, underscores). It's used to name your warehouse schemas.