platform-destructive-deploy

Handling Destructive Changes Coordinate metadata deletion against a Salesforce org via the destructiveChanges manifest. Runs in three phases: scope → validate → execute, with stricter guardrails for production. Phase 1 — Scope the deletion Step 1a — Gather the components to remove Ask the user (or infer from context) which components to delete. For each, capture: Metadata type (e.g. CustomObject , CustomField , ApexClass , Flow , PermissionSet ) API name (e.g. Project__c , Account.Status__c , MyController ) Step 1b — Local dependency scan (best-effort) Before generating the manifest, scan the local project for references to each component. Use Grep over force-app/ : grep -rn "" force-app/ --include = '.cls' --include = '.trigger' --include = '.xml' --include = '.js' --include = '*.html' Show more Installs 881 Repository forcedotcom/sf-skills GitHub Stars 835 First Seen 14 days ago Security Audits Gen Agent Trust Hub Pass Socket Warn Snyk Pass