PaperclipOrg
Claude Agent Skill · by Jaganpro

Sf Deploy

Install Sf Deploy skill for Claude Code from jaganpro/sf-skills.

Install
Terminal · npx
$npx skills add https://github.com/nextlevelbuilder/ui-ux-pro-max-skill --skill ui-ux-pro-max
Works with Paperclip

How Sf Deploy fits into a Paperclip company.

Sf Deploy drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md215 lines
Expand
---name: sf-deploydescription: >  Salesforce DevOps automation using sf CLI v2.  TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes,  sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy.  DO NOT TRIGGER when: writing Apex/LWC code (use sf-apex/sf-lwc), creating metadata  XML (use sf-metadata), or querying org data (use sf-data).license: MITmetadata:  version: "2.3.0"  author: "Jag Valaiyapathy"--- # sf-deploy: Comprehensive Salesforce DevOps Automation Use this skill when the user needs **deployment orchestration**: dry-run validation, targeted or manifest-based deploys, CI/CD workflow advice, scratch-org management, failure triage, or safe rollout sequencing for Salesforce metadata. ## When This Skill Owns the Task Use `sf-deploy` when the work involves:- `sf project deploy start`, `quick`, `report`, or retrieval workflows- release sequencing across objects, permission sets, Apex, and Flows- CI/CD gates, test-level selection, or deployment reports- troubleshooting deployment failures and dependency ordering 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)- authoring Agent Script logic → [sf-ai-agentscript](../sf-ai-agentscript/SKILL.md) --- ## Critical Operating Rules - Use **`sf` CLI v2 only**.- On non-source-tracking orgs, deploy/retrieve commands require an explicit scope such as `--source-dir`, `--metadata`, or `--manifest`.- Prefer **`--dry-run` first** before real deploys.- For Flows, deploy safely and activate only after validation.- Keep test-data creation guidance delegated to **`sf-data`** after metadata is validated or deployed. ### Default deployment order| Phase | Metadata ||---|---|| 1 | Custom objects / fields || 2 | Permission sets || 3 | Apex || 4 | Flows as Draft || 5 | Flow activation / post-verify | This ordering prevents many dependency and FLS failures. --- ## Required Context to Gather First Ask for or infer:- target org alias and environment type- deployment scope: source-dir, metadata list, or manifest- whether this is validate-only, deploy, quick deploy, retrieve, or CI/CD guidance- required test level and rollback expectations- whether special metadata types are involved (Flow, permission sets, agents, packages) Preflight checks:```bashsf --versionsf org listsf org display --target-org <alias> --jsontest -f sfdx-project.json``` --- ## Recommended Workflow ### 1. PreflightConfirm auth, repo shape, package directories, and target scope. ### 2. Validate first```bashsf project deploy start --dry-run --source-dir force-app --target-org <alias> --wait 30 --json```Use manifest- or metadata-scoped validation when the change set is targeted. ### 3. If validation succeeds, offer the next safe workflowAfter a successful validation, guide the user to the correct next action:1. deploy now2. assign permission sets3. create test data via [sf-data](../sf-data/SKILL.md)4. run tests / smoke checks5. orchestrate multiple post-deploy steps in order ### 4. Deploy the smallest correct scope```bash# source-dir deploysf project deploy start --source-dir force-app --target-org <alias> --wait 30 --json # manifest deploysf project deploy start --manifest manifest/package.xml --target-org <alias> --test-level RunLocalTests --wait 30 --json # manifest deploy with Spring '26 relevant-test selectionsf project deploy start --manifest manifest/package.xml --target-org <alias> --test-level RunRelevantTests --wait 30 --json # quick deploy after successful validationsf project deploy quick --job-id <validation-job-id> --target-org <alias> --json``` ### 5. Verify```bashsf project deploy report --job-id <job-id> --target-org <alias> --json```Then verify tests, Flow state, permission assignments, and smoke-test behavior. ### 6. Report clearlySummarize what deployed, what failed, what was skipped, and what the next safe action is. Output template: [references/deployment-report-template.md](references/deployment-report-template.md) --- ## High-Signal Failure Patterns | Error / symptom | Likely cause | Default fix direction ||---|---|---|| `FIELD_CUSTOM_VALIDATION_EXCEPTION` | validation rule or bad test data | adjust data or rule timing || `INVALID_CROSS_REFERENCE_KEY` | missing dependency | include referenced metadata first || `CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY` | trigger / Flow / validation side effect | inspect automation stack and failing logic || tests fail during deploy | broken code or fragile tests | run targeted tests, fix root cause, revalidate || field/object not found in permset | wrong order | deploy objects/fields before permission sets || Flow invalid / version conflict | dependency or activation problem | deploy as Draft, verify, then activate | Full workflows: [references/orchestration.md](references/orchestration.md), [references/trigger-deployment-safety.md](references/trigger-deployment-safety.md) --- ## CI/CD Guidance Default pipeline shape:1. authenticate2. validate repo / org state3. static analysis4. dry-run deploy5. tests + coverage gates6. deploy7. verify + notify - When org policy and release risk allow it, consider `--test-level RunRelevantTests` for Apex-heavy deployments.- Pair this with modern Apex test annotations such as `@IsTest(testFor=...)` and `@IsTest(isCritical=true)` as documented in `sf-apex`. Static analysis now uses **Code Analyzer v5** (`sf code-analyzer`), not retired `sf scanner`. Deep reference: [references/deployment-workflows.md](references/deployment-workflows.md) --- ## Agentforce Deployment Note Use this skill to orchestrate **deployment/publish sequencing** around agents, but use the agent-specific skills for authoring decisions:- [sf-ai-agentscript](../sf-ai-agentscript/SKILL.md) for `.agent` authoring and validation- [sf-ai-agentforce](../sf-ai-agentforce/SKILL.md) for Agent Builder / Prompt Builder / metadata config For full agent DevOps details, including `Agent:` pseudo metadata, publish/activate, and sync-between-orgs, see:- [references/agent-deployment-guide.md](references/agent-deployment-guide.md) --- ## Cross-Skill Integration | Need | Delegate to | Reason ||---|---|---|| custom object / field creation | [sf-metadata](../sf-metadata/SKILL.md) | define metadata before deploy || Apex compile / review / fixes | [sf-apex](../sf-apex/SKILL.md) | code authoring and repair || Flow creation / repair | [sf-flow](../sf-flow/SKILL.md) | Flow authoring and activation guidance || test data or seed records | [sf-data](../sf-data/SKILL.md) | describe-first data setup and cleanup || Agent Script build/publish readiness | [sf-ai-agentscript](../sf-ai-agentscript/SKILL.md) | agent-specific correctness | --- ## Reference Map ### Start here- [references/orchestration.md](references/orchestration.md)- [references/deployment-workflows.md](references/deployment-workflows.md)- [references/deployment-report-template.md](references/deployment-report-template.md) ### Specialized deployment safety- [references/trigger-deployment-safety.md](references/trigger-deployment-safety.md)- [references/agent-deployment-guide.md](references/agent-deployment-guide.md)- [references/deploy.sh](references/deploy.sh) --- ## Score Guide | Score | Meaning ||---|---|| 90+ | strong deployment plan and execution guidance || 75–89 | good deploy guidance with minor review items || 60–74 | partial coverage of deployment risk || < 60 | insufficient confidence; tighten plan before rollout | --- ## Completion Format ```textDeployment goal: <validate / deploy / retrieve / pipeline>Target org: <alias>Scope: <source-dir / metadata / manifest>Result: <passed / failed / partial>Key findings: <errors, ordering, tests, skipped items>Next step: <safe follow-up action>```