How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/sshvarzman-salesforce/claude-skills --skill sf-service-tooling-cicdBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Service Cloud CI/CD (Tooling API)
Use This Skill When
- Wiring Service Cloud metadata into a CI/CD pipeline (GitHub Actions, Jenkins, Copado).
- Enforcing Apex code coverage gates on triggers/classes exercised by routing, entitlements, or flows.
- Introspecting active Flow versions (e.g., Omni routing flow) before promoting a package.
- Auditing validation rules and custom fields on Case, VoiceCall, MessagingSession before a deploy.
- Running async test batches and blocking pipeline promotion on results.
Core Workflow
- Define the pipeline stage
- Pre-deploy: retrieve + diff metadata, run validation and static checks.
- Post-deploy: run async tests, evaluate coverage aggregates.
- Introspect the target org
- Query
FlowDefinition+Flowto confirm the expected active version is present after deploy. - Query
OmniProcessfor OmniScript/Integration Procedure states.
- Assert coverage
- Query
ApexCodeCoverageAggregatefor classes/triggers on the routing/entitlement path. - Fail the build when coverage drops below the org-defined floor for touched classes.
- Audit config
ValidationRuleandCustomFieldon Case, VoiceCall, MessagingSession — snapshot before/after to detect drift.
- Run tests async
POST /tooling/runTestsAsynchronouswith the list of classes; pollApexTestRunResultfor status; publish JUnit XML.
Deliverables
- CI stage definitions (pre-deploy checks, post-deploy asserts).
- Coverage floor per subsystem (case, entitlements, omni-routing, voice) with rationale.
- Drift detection queries for validation rules / custom fields with owning team.
- Test-run report format (JUnit + coverage summary) consumed by the CI provider.
References
- See
references/api-cli.mdfor exact Tooling API endpoints and object shapes.
