67
GitHub Stars
4
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill jaganpro/sf-skills --skill sf-deploy- CREDITS.md4.5 KB
- LICENSE1.1 KB
- README.md2.6 KB
- SKILL.md18.8 KB
Overview
This skill automates Salesforce DevOps using the modern sf CLI (v2.x) to manage metadata deployments, scratch orgs, CI/CD pipelines, and deployment troubleshooting. It enforces safe orchestration order for objects, permission sets, Apex, and flows, and produces actionable reports and remediation steps. Use it to validate, execute, and monitor deployments with built-in guardrails for production safety.
How this skill works
The skill inspects project metadata (sfdx-project.json, package.xml, source dirs) and orchestrates deploys using sf project deploy commands with --dry-run validation before execution. It parses deployment reports and error output, suggests fixes for common failures (FLS, missing dependencies, tests), and handles flow activation as a separate verification step. It also integrates with CI/CD flows, scratch org management, and post-deploy verification commands to produce a compact deployment summary.
When to use it
- Deploy metadata to sandboxes or production with sf CLI v2.x
- Run CI/CD pipelines that require validation gates and test coverage checks
- Create or manage scratch orgs and environment snapshots for feature work
- Troubleshoot deployment failures and get remediation guidance
- Deploy agent/AI metadata or orchestrate multi-component releases involving Apex and Flows
Best practices
- Always run sf project deploy start --dry-run before actual deployment
- Deploy custom objects/fields first, then permission sets, then Apex, then flows (deploy flows as Draft, then activate)
- Use manifest-based or targeted incremental deploys instead of large monolithic batches
- Run RunLocalTests or RunAllTests depending on environment; prefer RunAllTests for production packages
- Commit and tag releases; back up metadata before major changes and validate in sandbox first
- Use quick deploy after a successful validation to speed production rollouts
Example use cases
- Full release to production: validate with --dry-run, run RunAllTests, then quick deploy validated job
- Hotfix: targeted deploy of specific classes + RunLocalTests and immediate quick deploy
- CI pipeline: authenticate via JWT, static analysis, dry-run gate, tests, deploy and notify
- Agent deployment: deploy Apex then Flows, validate agent authoring bundle, publish and activate agent with required deactivation step
FAQ
Use sf CLI v2.x. The legacy sfdx (v1) commands and flags differ; for example, use --dry-run instead of --checkonly.
Why do flows deploy as Draft?
Flows deploy as Draft to allow validation before activation. After a successful draft deploy, edit XML to Active and redeploy to activate safely.
What common error means a dependency is missing?
INVALID_CROSS_REFERENCE_KEY or 'no CustomObject named' indicate missing objects/fields; deploy those dependencies first.