From orchestra
Retrofits dbt Slim CI onto an existing Orchestra production dbt pipeline using latest_production, state:modified+, and --defer, with GitHub Actions run-pipeline as the primary CI trigger. Use when setting up Orchestra Slim CI, dbt CI/CD in Orchestra, run-pipeline for dbt, or latest_production defer state in a dbt repo or from outside it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/orchestra:orchestra-dbt-slim-ci-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Retrofit **Slim CI** onto an **existing production dbt Orchestra pipeline** (one pipeline for prod and CI). Generate or patch repo artifacts, validate pipeline YAML, and leave a verification checklist. Do not assume warehouse or Git connections can be created via API.
Retrofit Slim CI onto an existing production dbt Orchestra pipeline (one pipeline for prod and CI). Generate or patch repo artifacts, validate pipeline YAML, and leave a verification checklist. Do not assume warehouse or Git connections can be created via API.
run-pipeline for dbt PR checks.latest_production.After setup, failed PR checks: use pr-slim-ci-orchestra-debug (project or org copy). Do not merge debug steps into this skill.
dbt_project.yml, profiles.yml, orchestra/, .github/workflows/. Outside: require repo URL, pipeline YAML path, and where GHA lives. If already configured per Orchestra docs, report and run verification only.list_pipelines; read YAML. Checklist: references/retrofit-checklist.md.update_pipeline. Orchestra-backed only: validate_pipeline then create_pipeline / update_pipeline.branch = pipeline YAML branch; dbt_branch only in run_inputs.latest_production (successful prod run on default branch).ORCHESTRA_API_KEY, optional pipeline/task id secrets, GHA environment → Orchestra environment mapping. Warehouse creds stay in Orchestra dbt connection.validate_pipeline when definition available; dbt parse when possible. start_pipeline with Slim runInputs only with user approval.latest_production.Non-GitHub CI (document start_pipeline MCP tool / CLI as follow-up), new warehouse/Git OAuth setup, Lightdash preview CI, auto-fixing failing Slim CI runs.
| Topic | URL |
|---|---|
| CI/CD for dbt Core | https://docs.getorchestra.io/docs/git-control-and-ci-cd/ci-cd/dbt_ci_cd |
| GitHub Actions CI/CD | https://docs.getorchestra.io/docs/git-control-and-ci-cd/ci-cd/github_actions |
| dbt Core execute | https://docs.getorchestra.io/docs/integrations/dbt_core/dbt_core_execute |
| Pipeline inputs | https://docs.getorchestra.io/docs/core-concepts/variables/inputs |
| dbt Core in Orchestra | https://docs.getorchestra.io/docs/guides/dbt-core/orchestra-setup |
Full input matrix and MCP steps: references/orchestra-slim-ci.md.
npx claudepluginhub orchestra-hq/orchestra-skills --plugin orchestraProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.