PranavNagrecha/AwesomeSalesforceSkills / .claude/skills/salesforce-devops
salesforce-devops
VerifiedRouter 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.
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 planchangeset-builder— Build or validate a deployment Change Set manifestdeployment-failure-triager— Diagnose an existing Salesforce deploy failuredeployment-risk-scorer— Risk-score a change set before deploymilestone-verifier— Cross-step verification + acceptance report for one milestonemulti-org-drift-analyzer— Multi-Org Drift Analysisrelease-readiness-reviewer— Release Readiness Reviewrelease-train-planner— Plan or audit a Salesforce release trainsandbox-strategy-designer— Design or audit sandbox + scratch-org strategystep-tester— Run the molecular tests for one built step
Rules
- Answer from the opened
devopspackage, never from this router. - Cite the skill id and, where one applied, the decision-tree branch.
- Never claim a topic is uncovered without pasting lookup output.
- Never deploy to an org.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |