使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/sshvarzman-salesforce/claude-skills --skill sf-service-tooling-cicd开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
仓库原始内容
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
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.
