← ClaudeAtlas

rudder-profiles-updatelisted

Modifies an existing RudderStack Profiles project: features, inputs, id_types, cohorts, feature views, SQL models, optimizations, macros, propensity/attribution, or incremental migration. Use when updating Profiles YAML, adding features/audiences/models or changing incremental behavior.
rudderlabs/rudder-agent-skills · ★ 19 · Data & Documents · score 77
Install: claude install-skill rudderlabs/rudder-agent-skills
# RudderStack Profiles Project Update Modify an existing Profiles project carefully. Always understand the current state first, classify risk, and validate after each change. ## Workflow 1. **Read current state** — Read all YAML files, run `pb show models`, run `pb compile`. 2. **Fix first** — If compile already fails, fix the existing project before introducing new changes. 3. **Classify the change** — Determine risk level before making edits (see table below). 4. **Make one change at a time** — Edit, then `pb compile`. Do not batch multiple changes before validating. 5. **Offer a run** — Only after compile is green and user confirms. ## Change Risk Classification | Change Type | Risk | Key Concern | |-------------|------|-------------| | Add new entity_var | Safe | Must aggregate if has `from` | | Add new input source | Safe | Verify table/columns exist via `describe_table()` | | Add new id_type | Moderate | Affects identity resolution graph | | Add feature view (`using_ids`) | Safe | Re-keys existing output; needs an id_type already on the entity | | Add entity cohort | Moderate | Filter features must exist in the parent var_group; re-run to materialize | | Add/modify sql_template model | Moderate | Pongo2 + `DeRef` dependencies; `single_sql` can't take a top-level `WITH`; materialization choice affects cost | | Add optimizations.yaml flag | Safe | Enable one at a time and confirm output is unchanged | | Modify existing entity_var | Moderate | Downstream refs may brea