skills.rest
SalesforceLabs
SalesforceLabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pde-org-build

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

5|3|Updated Sep 9, 2026
Search Tags:#build automation#feature flags#salesforce#pde#cumulusci#scratch org#revenue cloud
One-click install
npx skills add https://github.com/SalesforceLabs/revenue-cloud-foundations --skill pde-org-build-salesforcelabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pde-org-build
Source: https://github.com/SalesforceLabs/revenue-cloud-foundations/tree/main/.cursor/skills/pde-org-build
Command: npx skills add https://github.com/SalesforceLabs/revenue-cloud-foundations --skill pde-org-build-salesforcelabs

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, and long builds make it hard to tell success from a frozen log. This skill routes you to a self-reverting build script that handles flag overrides, scratch org provisioning, and cleanup automatically. ## 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 Shapes: Provisions a uniquely-aliased scratch org from the tfid-pde Trialforce snapshot by default, or from the dev-r1 Developer Edition shape via SHAPE=dev-r1. - Exit-Code Gating: Treats the script exit code as the authoritative success signal rather than the visible log tail, which caps around 1 MB and appears frozen mid-build. - Use Case: Schedule a Cursor Cloud Agent that runs the build nightly; each run creates a unique pde<datetimestamp><pid> alias so runs never collide, and git status confirms the working tree is clean afterward. ## Quick Start Run scripts/build_pde_dev_r1.sh to build a PDE org with the default tfid-pde shape and automatic cleanup.

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?▼

Run scripts/build_pde_dev_r1.sh, which provisions a fresh pde<datetimestamp><pid> scratch org from the tfid-pde shape, applies runtime flags pde=true and billing_ui=false, runs the prepare_rlm_org flow, and reverts all touched files on exit.

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

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

What is the difference between 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 used by setting SHAPE=dev-r1 when you want to build from a vanilla DE scratch instead of a snapshot.

Why does the build log appear frozen during a PDE build?▼

The captured terminal log caps around 1 MB and stops updating while the build keeps running. Gate any follow-up action on the script's exit code 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 fails fast if the target org alias already exists. Use CLEAN_BUILD_ARTIFACTS=false to skip the cleanliness check.

Can I schedule automated PDE builds with 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, but the scratch shape registration must be committed on the branch, not just present locally.

Related Skills

Explore More Software Engineering Skills→
KaiserWhoLearnsKaiserWhoLearns

Package Development Lifecycle

Automate Salesforce managed package workflows from design to production release.

Community
Advanced
WebDev70WebDev70

google-cloud-build-expert

Configure Google Cloud Build CI/CD pipelines with cloudbuild.yaml syntax.

Community
Advanced
ArthTech-AIArthTech-AI

ci-fix

Diagnose and fix GitHub Actions CI pipeline failures from failed run logs.

Official
Intermediate
ronmikailovronmikailov

rollback-changes

Automate rollback of failed workflow phases using a validated changes log.

Community
Advanced