pde-org-build

Builds Salesforce PDE scratch orgs with temporary self-reverting feature-flag overrides.

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill pde-org-build-drgaciw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pde-org-build
Source: https://github.com/drgaciw/rlm-base-dev-fork/tree/main/.cursor/skills/pde-org-build
Command: npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill pde-org-build-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a Partner Development Environment (PDE) org for Revenue Cloud requires temporary feature-flag changes (pde=true, billing_ui=false) that must never leak into committed configuration, plus a uniquely-aliased scratch org and reliable cleanup of build artifacts. This Skill routes you to a script that automates the entire build-and-revert workflow safely. ## Core Features & Use Cases - Self-Reverting Builds: Applies runtime-only flag overrides in cumulusci.yml and restores every touched file on exit, whether the build succeeds, fails, or is interrupted. - Flexible Org Provisioning: Provisions a fresh pde<datetimestamp><pid> scratch org from the tfid-pde Trialforce shape or the dev-r1 Developer-Edition shape, failing fast on alias collisions. - Cleanup Verification: Requires unpackaged/post_ux/ and datasets/sfdmu/ to be clean before running and reverts all build churn afterward, verifiable with git status. - Use Case: Schedule a nightly PDE build as a Cursor Cloud Agent that provisions a unique org, runs the prepare_rlm_org flow, and gates downstream notifications on the script's exit code rather than the truncated log tail. ## Quick Start Ask your agent to run scripts/build_pde_dev_r1.sh to build a PDE org with the default tfid-pde shape and verify the working tree is clean afterward.

Frequently Asked Questions about pde-org-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Salesforce PDE scratch org with CumulusCI?▼

Run scripts/build_pde_dev_r1.sh, which registers a fresh pde<datetimestamp><pid> scratch org from the tfid-pde shape, applies runtime flags pde=true and billing_ui=false, then runs the prepare_rlm_org flow. Override behavior with ORG, SHAPE, or FLOW environment variables.

How do I apply temporary feature flags without committing them?▼

The build script backs up cumulusci.yml, sets the flags only for the build duration, and restores the file via an EXIT trap on success, failure, or interrupt. Never commit pde or billing_ui flips to main; verify with git status afterward.

What is the difference between the tfid-pde and dev-r1 scratch shapes?▼

tfid-pde is a Trialforce-snapshot shape defined in orgs/tfid/tfid-pde.json and is the current default. dev-r1 is a standard Developer-Edition scratch config in orgs/internal/dev-r1.json; select it with SHAPE=dev-r1 to build from a vanilla DE scratch.

Why does the PDE build log appear frozen mid-build?▼

The captured terminal log caps around 1 MB and stops updating while the build continues running. Gate any follow-up action on the script's exit code (0 means success) or the exit_code footer, not the visible log tail.

Why does the PDE build script abort before starting?▼

The script requires unpackaged/post_ux/ and datasets/sfdmu/ to be clean so it never clobbers pre-existing local edits, and it aborts unless each flag matches exactly once in cumulusci.yml. Use CLEAN_BUILD_ARTIFACTS=false to skip the cleanliness check.

Can I schedule automated PDE builds as a cloud agent?▼

Yes, convert .cursor/commands/build-pde-dev-r1.md into a Cursor Cloud Agent; each run provisions a unique alias so runs never collide. Confirm the scratch shape registration is committed on the branch, or the cloud checkout's cci org scratch command will fail.