本文へ移動
cccskills
無料GitHub で公開

salesforce-devops

Router for the 70 SfSkills `devops` skill packages. Salesforce delivery: source tracking, packaging, branching, CI/CD pipelines, environment strategy and deployment troubleshooting. Use when the request mentions deploy, deployment, sfdx, sf CLI, scratch org, sandbox, unlocked package, change set, CI/CD, GitHub Actions, release, rollback, source tracking. Finds and opens the exact skill package to read; it does not contain the guidance itself.

PranavNagrecha/AwesomeSalesforceSkills
インストール方法を見る

含まれるファイル（2）

  • SKILL.md4.9 KB
  • references/skill-index.md19.4 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Salesforce devops — SfSkills domain router

Salesforce delivery: source tracking, packaging, branching, CI/CD pipelines, environment strategy and deployment troubleshooting.

70 skill packages live under ${CLAUDE_PLUGIN_ROOT}/skills/devops/<slug>/SKILL.md. They are not loaded — reach them by path, on demand.

Generated by scripts/build_plugin.py. Do not hand-edit.

How to find the right skill

Three mechanisms, listed in order of reliability on a fresh install. Use the first one that is available; do not stop at a guess.

1. The shipped roster (always works, no setup). Read references/skill-index.md next to this file. It lists every devops skill package with a one-line gloss, generated from registry/skills.json. Scan it and pick by name.

2. The MCP server (fast, needs the sfskills-mcp server connected). Call the search_skill tool with the user's phrasing and domain: "devops". It returns ranked skill ids. get_skill then returns the package contents.

3. The search CLI (fast, needs a locally built index).

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/search_knowledge.py" "<the user's question>" --domain devops --json

This needs vector_index/, which is not shipped — it is gitignored and must be built once per clone:

cd "${CLAUDE_PLUGIN_ROOT}" && python3 -m pip install -r requirements.txt && python3 scripts/build_index.py

If the command errors or reports Coverage: NONE, fall back to mechanism 1 rather than telling the user the topic is uncovered.

Then read the package. Open the exact ${CLAUDE_PLUGIN_ROOT}/skills/<domain>/<slug>/SKILL.md the lookup returned, plus its references/gotchas.md and references/llm-anti-patterns.md. Do not answer from this router: it is a map, not the territory.

Featured entry points

Curated starting points when the request is broad or the lookup is ambiguous. This is a shortlist, not the catalogue — the roster at references/skill-index.md has all 70.

  • ${CLAUDE_PLUGIN_ROOT}/skills/devops/salesforce-dx-project-structure/SKILL.md — project layout, sfdx-project.json, and package directories
  • ${CLAUDE_PLUGIN_ROOT}/skills/devops/environment-strategy/SKILL.md — sandbox tiers, scratch orgs, and what each environment is allowed to prove
  • ${CLAUDE_PLUGIN_ROOT}/skills/devops/git-branching-for-salesforce/SKILL.md — a branching model that survives metadata merge conflicts
  • ${CLAUDE_PLUGIN_ROOT}/skills/devops/release-management/SKILL.md — release trains, cutover windows, and change control
  • ${CLAUDE_PLUGIN_ROOT}/skills/devops/pre-deployment-checklist/SKILL.md — the go/no-go gate before a production deploy
  • ${CLAUDE_PLUGIN_ROOT}/skills/devops/deployment-error-diagnosis/SKILL.md — decoding the deploy failures that do not say what is wrong
  • ${CLAUDE_PLUGIN_ROOT}/skills/devops/unlocked-package-development/SKILL.md — packaging as the modularisation strategy, with dependency ordering
  • ${CLAUDE_PLUGIN_ROOT}/skills/devops/github-actions-for-salesforce/SKILL.md — a working CI pipeline: auth, validate, test, deploy

Decision trees

Read the tree before activating a skill when the request could be solved more than one way, and cite the branch that decided it.

  • ${CLAUDE_PLUGIN_ROOT}/standards/decision-trees/automation-selection.md — no devops-specific tree exists yet; the Flow-vs-Apex choice drives deployment ordering and packaging boundaries

Run-time agents for this domain

Invoke one of these subagents when the ask is a whole workflow rather than a single question:

  • build-step-runner — Execute one step of a build plan
  • changeset-builder — Build or validate a deployment Change Set manifest
  • deployment-failure-triager — Diagnose an existing Salesforce deploy failure
  • deployment-risk-scorer — Risk-score a change set before deploy
  • milestone-verifier — Cross-step verification + acceptance report for one milestone
  • multi-org-drift-analyzer — Multi-Org Drift Analysis
  • release-readiness-reviewer — Release Readiness Review
  • release-train-planner — Plan or audit a Salesforce release train
  • sandbox-strategy-designer — Design or audit sandbox + scratch-org strategy
  • step-tester — Run the molecular tests for one built step

Rules

  1. Answer from the opened devops package, never from this router.
  2. Cite the skill id and, where one applied, the decision-tree branch.
  3. Never claim a topic is uncovered without pasting lookup output.
  4. Never deploy to an org.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

acceptance-criteria-given-when-then

無料

Use this skill when writing test-first, behavior-driven acceptance criteria in Given/When/Then format for a Salesforce user story. Covers happy path, edge cases, negative paths, permission boundaries, and data-state preconditions so the AC block can drive UAT scripts and Apex test design downstream. Trigger keywords: given when then, gherkin, behavior driven AC, test first acceptance criteria, scenario outline, BDD acceptance criteria. NOT for the user-story format itself (use admin/user-story-writing-for-salesforce). NOT for UAT script writing (use admin/uat-test-case-design). NOT for Apex test method generation (use agents/test-class-generator). NOT for high-level UAT planning (use admin/uat-and-acceptance-criteria). More triggers: acceptance criteria record, ac_id, req_id on a criterion, artefact under test, negative case for a rule-type requirement, no-match fall-through criterion, oracle for a Then clause, test type apex flow manual, criteria linter, check_ac_format.py, --manifest-dir.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

activity-and-task-patterns

無料

Task and Event objects: polymorphic WhatId/WhoId, Activity object model, ActivityHistory vs OpenActivity, activity timeline customization, bulk task creation, Einstein Activity Capture boundaries. NOT for turning on EAC or calendar sync — use admin/einstein-activity-capture-setup. NOT for Email-to-Case — use admin/case-management-setup. Covers ActivitiesSettings metadata, enableActivities, shared Task/Event custom fields and FLS, TaskStatus value sets, Shared Activities and TaskRelation/EventRelation, recurring and child activities, and partial-success bulk DML on Task.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

agent-action-error-handling

無料

Design Invocable Apex actions that return deterministic, agent-friendly errors instead of surfacing raw exceptions to the LLM. NOT for authoring the action itself — @InvocableMethod schema, labels, security context — use agentforce/custom-agent-actions-apex. NOT for the Apex tests that force each error branch — use agentforce/agent-action-unit-tests.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

agent-action-input-slot-extraction

無料

Use when designing how an Agentforce agent extracts structured input parameters (slots) from a user's natural-language utterance to invoke an action. Triggers: 'agent extract date from user', 'agent action argument extraction', 'agentforce slot filling', 'agent invocable input mapping', 'agent fails to fill required parameter'. NOT for action authoring (use agentforce/agent-actions) or for prompt-template variable binding (use agentforce/prompt-builder-templates).

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

agent-action-unit-tests

無料

Apex test patterns for @InvocableMethod agent actions: per-reason-code branch coverage, bulk safety, callout mocking, deterministic assertions. NOT for testing whether the agent routes to the right topic or answers well — use agentforce/agent-testing-and-evaluation. NOT for designing the error envelope the tests assert on — use agentforce/agent-action-error-handling.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

agent-actions

無料

Designing or reviewing Agentforce actions: Flow actions, Apex invocable actions, prompt-template actions, action naming, input and output contracts, confirmation requirements, and safe error behavior. Triggers: 'agent actions', 'build an agent that can look up an order', 'make the agent able to check order status', 'give the agent a capability', 'agent that can retrieve a record', 'flow action for agent', 'agent invocable action', 'action schema design'. NOT for writing the Apex class itself — use agentforce/custom-agent-actions-apex. NOT for the reason_code error envelope that stops an agent retry loop — use agentforce/agent-action-error-handling.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

PranavNagrecha のスキルをすべて見る

このスキルの問題を報告する