Run any Skill in Manus with one click

dx-devops-test-pipeline-configure

Stars639

Forks223

UpdatedJune 26, 2026 at 17:15

Configures DevOps Center pipeline testing infrastructure: enables a test provider so its suites become available, re-syncs a configured provider to pull in new suites, or creates a quality gate with rules on a stage. Routes by intent across three modes after running shared prerequisite checks and an explicit confirmation gate. Use this skill when a user wants to set up, configure, enable, sync, or refresh a test provider, or set/configure a quality gate or coverage threshold on a DevOps Center pipeline stage. TRIGGER when: the user wants to configure/enable/add/set up a test provider, re-sync or refresh a provider's suite list, pull in new suites, or set/configure a quality gate, coverage threshold, or testing benchmark on a stage. DO NOT TRIGGER when: assigning existing suites to a stage (use dx-devops-test-suite-assignments-configure), running or retriggering a suite (use dx-devops-test-suite-run), or non-DevOps-Center work.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

forcedotcom

forcedotcom/sf-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

File Explorer

7 files

SKILL.md

readonly

name	dx-devops-test-pipeline-configure
description	Configures DevOps Center pipeline testing infrastructure: enables a test provider so its suites become available, re-syncs a configured provider to pull in new suites, or creates a quality gate with rules on a stage. Routes by intent across three modes after running shared prerequisite checks and an explicit confirmation gate. Use this skill when a user wants to set up, configure, enable, sync, or refresh a test provider, or set/configure a quality gate or coverage threshold on a DevOps Center pipeline stage. TRIGGER when: the user wants to configure/enable/add/set up a test provider, re-sync or refresh a provider's suite list, pull in new suites, or set/configure a quality gate, coverage threshold, or testing benchmark on a stage. DO NOT TRIGGER when: assigning existing suites to a stage (use dx-devops-test-suite-assignments-configure), running or retriggering a suite (use dx-devops-test-suite-run), or non-DevOps-Center work.
metadata	{"version":"1.0","minApiVersion":"67.0"}

Configure DevOps Center Pipeline Testing Infrastructure

Sets up and configures a DevOps Center pipeline's testing infrastructure. This skill handles three closely related "configure your pipeline" operations that share the same org context, prerequisites, and entity scope (the pipeline level). Pick the mode that matches the user's intent.

API version: All DevOps testing system calls target Salesforce API v67.0 (minimum required).

Important: All DevOps Center data (pipelines, stages, providers, suites, gates) lives in the Salesforce org — NOT the local repo. Never search the filesystem for pipeline configuration. Always query the org with sf data query or sf api request rest.

Step 1 — Run prerequisites first (always)

Before any query or system call, run the prerequisite checks in references/prerequisite-checks.md. On any failure, surface the plain-language message and stop — never write to an unverified environment.

Modes A & B (provider configure/sync): run Prerequisites 1–4 (org login, Agentforce DX plugin, DevOps Center org auth, pipeline identified). Prerequisite 5 (stage) is not required — providers are configured at the pipeline level.
Mode C (quality gate): run Prerequisites 1–4 and Prerequisite 5 (stage). Prereq 5 gives the DevopsPipelineStage only — the target DevopsTestSuiteStage record Id is resolved separately in Mode C's Step 0 (trigger → suite-stage row).

Carry forward the resolved doce-org-alias, pipelineId, and (Mode C) stageId / testSuiteStageId.

Step 2 — Select the mode

If the user wants to…	Mode	Follow
Enable / set up / add a provider that is not yet configured	A — Configure a test provider	`references/configuring-test-provider.md`
Re-sync / refresh an already-configured provider to pull in new suites	B — Sync a configured provider	`references/syncing-test-providers.md`
Set / configure a quality gate, coverage threshold, or testing benchmark on a stage	C — Configure a quality gate	`references/configuring-quality-gate.md`

Disambiguating A vs B (the critical decision): First fetch the pipeline's providers (GET .../testProviders?status=all) — both modes start there. Then:

Provider is Available (not configured) → Mode A (configure).
Provider is Configured but suites are stale/missing → Mode B (sync).
Provider is Configured and the user can't see suites when assigning to a stage → this is a stage-assignment gap, not a configuration gap. Redirect to dx-devops-test-suite-assignments-configure.

⚠ Never POST to the configure endpoint for an already-configured provider — it creates duplicate DevopsPipelineTestProvider records. See references/gotchas.md.

Step 3 — Confirmation gate (required in every mode)

Every mode mutates org state and must show a confirmation gate before any write. Each mode's reference file contains its exact gate wording (Mode C additionally requires a mandatory impact preview before the gate). Do not call any write API until the user gives an affirmative response. If the user declines, stop without writing.

Step 4 — Execute and report

Follow the chosen reference file for the exact API calls, success messages, and error handling:

references/configuring-test-provider.md — Mode A
references/syncing-test-providers.md — Mode B
references/configuring-quality-gate.md — Mode C
references/error-handling.md — consolidated status-code → plain-language tables for all modes
references/gotchas.md — duplicate-provider trap, API-name differences, trigger-type rules

Never expose raw API errors, stack traces, or JSON payloads to the user — always translate to plain language.

Related skills

dx-devops-test-suite-assignments-configure — after configuring/syncing a provider, assign or map its suites to a stage; also recommends which suites to run for a commit.
dx-devops-test-suite-run — run a suite, or retrigger a quality gate after fixes meet the threshold.
dx-devops-test-failures-analyze — explain failures from a run and optionally create a fix work item.

More from this repository

same repository

dx-devops-test-failures-analyze

forcedotcom/sf-skills

Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement suggestions (test-code vs production-code) — then optionally creates a tracked fix WorkItem on explicit request. Analysis is pure reasoning; work-item creation is a confirmation-gated write. Use this skill to explain failures or improvement suggestions, translate Code Analyzer violations, or track a fix as a work item. TRIGGER when: a run failed and the user wants root cause; a quality gate failure needs explaining; violations need translating; the user shares a failure payload and asks how to address it; wants to strengthen tests; or wants to create a fix work item, log a remediation, or assign a failure. DO NOT TRIGGER when: the user wants fix code written (use platform-apex-generate) or new test classes authored (use platform-apex-test-generate).

2026-06-29639

dx-devops-test-suite-assignments-configure

forcedotcom/sf-skills

Recommends and manages DevOps Center test suite assignments for pipeline stages. Mode A analyzes a commit diff against assigned suite metadata to recommend relevant existing suites and flag coverage gaps (pure reasoning). Modes B-D assign a single suite, bulk-map multiple suites with a mandatory impact preview, or add/remove test classes with governance rules, via the testSuiteStages Connect API. Use this skill to recommend suites for a commit, assign or map suites to stages, or add/remove tests in a suite. TRIGGER when: the user asks which suites to run for a commit/diff or what covers their changes; a suite is unlinked and the user wants it assigned; the user wants to configure suite-to-stage mappings, assign multiple suites, or add/remove/sync tests in a suite. DO NOT TRIGGER when: configuring or syncing a test provider (use dx-devops-test-pipeline-configure), running suites (use dx-devops-test-suite-run), or authoring/running tests directly (use platform-apex-test-generate or platform-apex-test-run).

2026-06-29639

dx-devops-test-suite-run

forcedotcom/sf-skills

Runs DevOps Center test suites on a pipeline stage (Pre-Promote, Post-Promote, or Review event) end to end: triggers async execution via the Connect API after an explicit confirmation gate, then polls by runId at provider-specific intervals until it completes, fails, or times out, and hands results to failure analysis. Also retriggers a quality gate after fixes, but only once coverage meets the threshold. Use this skill when a user wants to run, kick off, or launch test suites on a stage, re-run a quality gate, or watch an in-progress run to completion. TRIGGER when: the user wants to run/launch suites on a stage, execute tests before or after promotion, re-run a quality gate after fixing failures, unblock a blocked promotion after adding tests, or poll/watch an in-progress run. DO NOT TRIGGER when: running sf apex run test directly (use platform-apex-test-run), or configuring a NEW gate or threshold (use dx-devops-test-pipeline-configure).

2026-06-29639

commerce-b2b-open-code-components-replace

forcedotcom/sf-skills

Replace OOTB (out-of-the-box) B2B Commerce components with open source equivalents in site metadata content.json files, or look up the equivalent open code `site:` component for OOTB definitions. Use when users mention "replace OOTB components", "replace commerce components with open code", "swap OOTB for open source", "replace commerce_builder:", "replace OOTB in site", "replace component in site metadata", "replace component definition", "find open code equivalent", "equivalent open code component", "OOTB to open code mapping", "what is the site component for", components "in this view" or "for a given view", or a specific list of component names — and want to update or only discover mappings in their store metadata.

2026-06-26639

dx-org-manage

forcedotcom/sf-skills

INVOKE this skill to execute Salesforce org operations: create scratch orgs, create org snapshots, open orgs in browser. This skill EXECUTES operations immediately - it does NOT generate scripts or code files. ALWAYS invoke this skill (do not execute SF CLI commands directly) when user requests to: create a scratch org (Developer/Enterprise edition, from definition file (.json), from snapshot, or from org shape), create an org snapshot, or open a Salesforce org. Trigger phrases include: 'create a snapshot', 'create snapshot of my scratch org', 'take a snapshot', 'create scratch org', 'create a Developer edition scratch org', 'new scratch org', 'spin up an org', 'create org from snapshot', 'scratch-def.json', 'project-scratch-def.json', 'open my Salesforce org', 'open org in browser', 'get me the URL'. Do NOT use for switching default org (use dx-org-switch) or deploying metadata (use platform-metadata-deploy).

2026-06-26639

dx-org-permission-set-assign

forcedotcom/sf-skills

ALWAYS USE THIS SKILL to assign permission sets to org users. Assign one or more permission sets to org users using the sf org assign permset command. TRIGGER when the user asks to assign, grant, give, add, or apply permission sets to users, admins, specific orgs, or specific users. Supports granting permissions, giving access, and adding permission sets to default admin or specific users via --on-behalf-of. DO NOT TRIGGER for listing permission sets or checking user permissions.

2026-06-26639

name	dx-devops-test-pipeline-configure
description	Configures DevOps Center pipeline testing infrastructure: enables a test provider so its suites become available, re-syncs a configured provider to pull in new suites, or creates a quality gate with rules on a stage. Routes by intent across three modes after running shared prerequisite checks and an explicit confirmation gate. Use this skill when a user wants to set up, configure, enable, sync, or refresh a test provider, or set/configure a quality gate or coverage threshold on a DevOps Center pipeline stage. TRIGGER when: the user wants to configure/enable/add/set up a test provider, re-sync or refresh a provider's suite list, pull in new suites, or set/configure a quality gate, coverage threshold, or testing benchmark on a stage. DO NOT TRIGGER when: assigning existing suites to a stage (use dx-devops-test-suite-assignments-configure), running or retriggering a suite (use dx-devops-test-suite-run), or non-DevOps-Center work.
metadata	{"version":"1.0","minApiVersion":"67.0"}

Configure DevOps Center Pipeline Testing Infrastructure

API version: All DevOps testing system calls target Salesforce API v67.0 (minimum required).

Step 1 — Run prerequisites first (always)

Modes A & B (provider configure/sync): run Prerequisites 1–4 (org login, Agentforce DX plugin, DevOps Center org auth, pipeline identified). Prerequisite 5 (stage) is not required — providers are configured at the pipeline level.
Mode C (quality gate): run Prerequisites 1–4 and Prerequisite 5 (stage). Prereq 5 gives the DevopsPipelineStage only — the target DevopsTestSuiteStage record Id is resolved separately in Mode C's Step 0 (trigger → suite-stage row).

Carry forward the resolved doce-org-alias, pipelineId, and (Mode C) stageId / testSuiteStageId.

Step 2 — Select the mode

If the user wants to…	Mode	Follow
Enable / set up / add a provider that is not yet configured	A — Configure a test provider	`references/configuring-test-provider.md`
Re-sync / refresh an already-configured provider to pull in new suites	B — Sync a configured provider	`references/syncing-test-providers.md`
Set / configure a quality gate, coverage threshold, or testing benchmark on a stage	C — Configure a quality gate	`references/configuring-quality-gate.md`

Disambiguating A vs B (the critical decision): First fetch the pipeline's providers (GET .../testProviders?status=all) — both modes start there. Then:

Provider is Available (not configured) → Mode A (configure).
Provider is Configured but suites are stale/missing → Mode B (sync).
Provider is Configured and the user can't see suites when assigning to a stage → this is a stage-assignment gap, not a configuration gap. Redirect to dx-devops-test-suite-assignments-configure.

⚠ Never POST to the configure endpoint for an already-configured provider — it creates duplicate DevopsPipelineTestProvider records. See references/gotchas.md.

Step 3 — Confirmation gate (required in every mode)

Step 4 — Execute and report

Follow the chosen reference file for the exact API calls, success messages, and error handling:

references/configuring-test-provider.md — Mode A
references/syncing-test-providers.md — Mode B
references/configuring-quality-gate.md — Mode C
references/error-handling.md — consolidated status-code → plain-language tables for all modes
references/gotchas.md — duplicate-provider trap, API-name differences, trigger-type rules

Never expose raw API errors, stack traces, or JSON payloads to the user — always translate to plain language.

Related skills

dx-devops-test-suite-assignments-configure — after configuring/syncing a provider, assign or map its suites to a stage; also recommends which suites to run for a commit.
dx-devops-test-suite-run — run a suite, or retrigger a quality gate after fixes meet the threshold.
dx-devops-test-failures-analyze — explain failures from a run and optionally create a fix work item.