sf-deploylisted

<!-- Adapted from Jaganpro/sf-skills@ff1ab74 (MIT). This file layers Brite conventions from brite-salesforce/CLAUDE.md. --> # sf-deploy: Salesforce Deploy Orchestration (Brite edition) Deploy orchestration for the **brite-salesforce** repo: dry-run validation, targeted or manifest-based deploys, post-deploy Tooling API verification, `.forceignore` toggle discipline, Screen Flow activation, Scheduled Apex recovery, Named Credential PLACEHOLDER handling. CI/CD guidance pointing at Brite's scratch-org-per-PR pipeline. ## When This Skill Owns the Task Use `sf-deploy` when the work involves: - `sf project deploy start`, `quick`, `report`, or retrieval workflows in brite-salesforce - release sequencing across objects, permission sets, Apex, and Flows - cross-org metadata moves (sandbox ↔ production) with `.forceignore` toggles - post-deploy verification via Tooling API SOQL - Screen Flow activation, Scheduled Apex re-scheduling, Named Credential URL setup Delegate elsewhere when the user is: - authoring Apex or LWC code → [sf-apex](../sf-apex/SKILL.md), [sf-lwc](../sf-lwc/SKILL.md) - creating metadata definitions → [sf-metadata](../sf-metadata/SKILL.md) - building Flows → [sf-flow](../sf-flow/SKILL.md) - doing org data operations → [sf-data](../sf-data/SKILL.md) > **Default recommendation for brite-salesforce deploys**: prefer [`/revops:deploy-sandbox`](../../commands/deploy-sandbox.md) (sandbox) or [`/revops:deploy-prod`](../../commands/deploy-prod.md) (production) over raw