Salesforce Devops

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:

• changeset-builder — Build or validate a deployment Change Set manifest
• deployment-risk-scorer — Risk-score a change set before deploy
• release-train-planner — Plan or audit a Salesforce release train
• sandbox-strategy-designer — Design or audit sandbox + scratch-org strategy

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.