pde-org-build

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

33|12|Updated Sep 24, 2024
One-click install
npx skills add https://github.com/bgaldino/rlm-base-dev --skill pde-org-build-bgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pde-org-build
Source: https://github.com/bgaldino/rlm-base-dev/tree/main/.cursor/skills/pde-org-build
Command: npx skills add https://github.com/bgaldino/rlm-base-dev --skill pde-org-build-bgaldino

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. Doing this by hand risks committing flag flips, clobbering local edits, or misreading a truncated build log as success. ## Core Features & Use Cases - Self-reverting build script: Runs scripts/build_pde_dev_r1.sh to provision a fresh pde<datetimestamp><pid> scratch org from the tfid-pde shape, apply runtime-only flags, execute the prepare_rlm_org flow, and restore every touched file on exit. - Configurable overrides: Control the build via environment variables such as ORG, SHAPE, FLOW, and CLEAN_BUILD_ARTIFACTS, including switching to the dev-r1 Developer Edition scratch shape. - Safe scheduling and verification: Gate follow-up actions on the script exit code rather than the visible log tail, and verify cleanliness with git status after the run. - Use Case: A developer needs a clean PDE org for a Revenue Cloud demo. They run the script, which fails fast if the alias exists, builds the org with temporary flags, and leaves the working tree untouched. ## Quick Start Ask your agent to build a PDE org by running scripts/build_pde_dev_r1.sh and confirm success from its exit code and a clean git status.

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 for Revenue Cloud?

Run scripts/build_pde_dev_r1.sh, which provisions a uniquely-aliased scratch org from the tfid-pde shape, applies runtime-only pde and billing_ui flags, and runs the prepare_rlm_org flow. All file changes are reverted automatically on exit.

How do I apply temporary feature flags in cumulusci.yml without committing them?

The build script backs up cumulusci.yml, sets pde=true and billing_ui=false for the build duration only, and restores the file via an EXIT trap on success, failure, or interrupt. Never commit these flag flips to main.

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

tfid-pde is a Trialforce-snapshot shape and the current default for PDE builds. dev-r1 is a standard Developer Edition scratch config; select it with SHAPE=dev-r1 to build from a vanilla DE scratch org instead.

Why does the PDE build log appear frozen before the build finishes?

The captured terminal log caps around 1 MB and appears to freeze mid-build while the build keeps running. Treat the script exit code and the exit_code footer as the authoritative success signal, 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 fails fast if the target org alias already exists. Use CLEAN_BUILD_ARTIFACTS=false to skip the cleanliness check.

Can I schedule a PDE build as a Cursor 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. Ensure the scratch shape registration is committed on the branch, or the cloud checkout will fail.