Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/sshvarzman-salesforce/claude-skills --skill sf-service-tooling-cicdAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
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.


