sshvarzman-salesforce/claude-skills

sf-service-tooling-cicd

Tooling API patterns for Service Cloud CI/CD.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/sshvarzman-salesforce/claude-skills --skill sf-service-tooling-cicd

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

  1. Define the pipeline stage
  • Pre-deploy: retrieve + diff metadata, run validation and static checks.
  • Post-deploy: run async tests, evaluate coverage aggregates.
  1. Introspect the target org
  • Query FlowDefinition + Flow to confirm the expected active version is present after deploy.
  • Query OmniProcess for OmniScript/Integration Procedure states.
  1. Assert coverage
  • Query ApexCodeCoverageAggregate for classes/triggers on the routing/entitlement path.
  • Fail the build when coverage drops below the org-defined floor for touched classes.
  1. Audit config
  • ValidationRule and CustomField on Case, VoiceCall, MessagingSession — snapshot before/after to detect drift.
  1. Run tests async
  • POST /tooling/runTestsAsynchronous with the list of classes; poll ApexTestRunResult for 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.md for exact Tooling API endpoints and object shapes.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
sshvarzman-salesforce
커뮤니티

activating-datacloud

Salesforce Data Cloud Act phase. Use this skill when the user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. TRIGGER when: user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. DO NOT TRIGGER when: the task is segment creation (use segmenting-datacloud), data retrieval/search work (use retrieving-datacloud), or STDM/session tracing (use observing-agentforce).

설치 수
1
GitHub Stars
0
업데이트
10월 15일
sshvarzman-salesforce
커뮤니티

agentforce-skills-research

Research Agentforce configuration patterns — topics, actions, instructions, CLTs, knowledge, planner behavior. Searches Salesforce docs, Trailhead, internal repos (git.soma), Slack channels, and Google Docs to find working examples, known issues, and best practices.

설치 수
1
GitHub Stars
0
업데이트
10월 15일
sshvarzman-salesforce
커뮤니티

harmonizing-datacloud

Salesforce Data Cloud Harmonize phase. Use this skill when the user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. TRIGGER when: user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. DO NOT TRIGGER when: the task is only about streams/DLOs (use preparing-datacloud), segments/insights (use segmenting-datacloud), retrieval/search (use retrieving-datacloud), or STDM/sessio

설치 수
1
GitHub Stars
0
업데이트
10월 15일
sshvarzman-salesforce
커뮤니티

preparing-datacloud

Salesforce Data Cloud Prepare phase. Use this skill when the user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations. TRIGGER when: user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations, or asks about ingestion into Data Cloud. DO NOT TRIGGER when: the task is connection setup only (use connecting-datacloud), DMOs and identity resolution (use harmonizing-datacloud), or query/search work (use retrieving-datacloud)

설치 수
1
GitHub Stars
0
업데이트
10월 15일