dx-packaging-push-upgrade-configure
Installation
SKILL.md
Plan and drive a Salesforce package push upgrade end-to-end: find subscriber orgs, resolve the
target version, batch a schedule per best practices, generate the org CSV, run the sf CLI
push-upgrade commands after explicit confirmation, and monitor the results.
Push upgrades change a package in the customer's org without their action. This is outward-facing
and hard to reverse. The default posture of this skill is generate → preview → confirm → run:
never call push-upgrade schedule or push-upgrade abort until the user has seen the batch plan and
the org list and said go. See references/best-practices.md before scheduling anything to production.
Inputs
Gather these from the user's request; parse identifiers loosely wherever they appear:
- A token starting with
033→ the package ID (MetadataPackageIdfor queries,--packageforlist). - A token starting with
04t→ the target package version ID (--packageforschedule). - A token starting with
0DV→ an existing push request ID (jump straight to Phase 5, monitoring). - A Dev Hub alias or username → the org the push-upgrade objects and commands run against.