dbt-ci
Use when generating GitHub Actions workflows for dbt, adding dbt build/test/docs steps, or configuring state-based selection with --select state:modified+. Provides templates for both full builds (CD) and incremental builds (CI).
What this skill does
# dbt CI
## GitHub Actions Steps
### Full Build (CD / Production Baseline)
Use for production baseline workflows where you build everything:
**If uv:**
```yaml
- name: Run dbt
run: |
uv run dbt deps
uv run dbt build --target {TARGET}
uv run dbt docs generate --target {TARGET}
```
**If pip:**
```yaml
- name: Run dbt
run: |
source .venv/bin/activate
dbt deps
dbt build --target {TARGET}
dbt docs generate --target {TARGET}
```
### Incremental Build (CI / Pull Requests)
Use `--state` for state-based selection when comparing against a baseline:
**If uv:**
```yaml
- name: Run dbt (modified models only)
run: |
uv run dbt deps
uv run dbt build --target {TARGET} --select state:modified+ --state {STATE_PATH}
uv run dbt docs generate --target {TARGET} --select state:modified+ --state {STATE_PATH}
```
**If pip:**
```yaml
- name: Run dbt (modified models only)
run: |
source .venv/bin/activate
dbt deps
dbt build --target {TARGET} --select state:modified+ --state {STATE_PATH}
dbt docs generate --target {TARGET} --select state:modified+ --state {STATE_PATH}
```
## Variables
| Variable | Description | Example |
|----------|-------------|---------|
| `{TARGET}` | dbt target/profile name | `prod`, `ci`, `dev` |
| `{STATE_PATH}` | Path to baseline manifest for comparison | `target-base` |
## State-Based Selection
- `state:modified` - Only models with code changes
- `state:modified+` - Modified models + downstream dependencies
- `+state:modified+` - Upstream + modified + downstream
Requires `--state <path>` pointing to a directory with baseline `manifest.json`.
## Best Practices
- Use `state:modified+` in CI to only rebuild what changed
- Always run `dbt docs generate` to create artifacts for comparison tools
- Match `--target` to your profiles.yml environment (prod, ci, dev)
- Ensure baseline manifest exists before using `--state` flag
## Related Skills
- Use `python-uv-ci` skill for Python/uv environment setup steps
- Use `python-pip-ci` skill for Python/pip environment setup steps
- Use `recce-cloud-ci` skill for Recce Cloud upload/download steps
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.