dx-devops-test-suite-assignments-configure
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
Security Assessment
About dx-devops-test-suite-assignments-configure
This Salesforce skill recommends and manages DevOps Center test-suite assignments for pipeline stages. It has four modes: Mode A (pure reasoning, no writes) analyzes a commit diff against assigned suite metadata to recommend relevant existing suites and flag coverage gaps, while Modes B–D assign a single suite, bulk-map multiple suites, or add/remove test classes within a suite via the testSuiteStages Connect API. It solves the problem of knowing which test suites cover a given change and keeping suite-to-stage mappings correct within Salesforce DevOps Center.
The workflow enforces a shared prerequisite gate before any query or system call — verifying an authenticated Salesforce org, the Agentforce DX plugin, DevOps Center org authentication, and an identified pipeline (and stage for write modes) — using standard sf CLI commands (sf org list, sf plugins, sf org display, sf data query). It stresses that DevOps Center data lives in the org, not the local filesystem, and that queries target standard platform objects (DevopsPipeline, DevopsTestSuite, DevopsTestSuiteStage, etc.) at API v67.0 rather than legacy managed-package objects. Write modes are protected by governance: Mode C requires a mandatory impact-preview table and Mode D re-presents the final test list, and no API call is made without explicit user confirmation.
Target users are Salesforce developers and DevOps engineers configuring quality gates and test coverage in DevOps Center pipelines. All operations use official Salesforce CLI tooling and authenticated Connect API calls; the org-mutating modes are read-then-confirm with explicit approval gates, so the security profile is that of standard, well-guarded platform administration.
FAQ
What are the four modes?
Mode A recommends which existing suites to run for a commit and flags coverage gaps (pure reasoning, no writes). Mode B assigns a single suite to a stage, Mode C bulk-maps multiple suites with a mandatory impact preview, and Mode D adds or removes individual test classes within a suite assignment — all via the testSuiteStages Connect API.
What do I need before running it?
It runs a prerequisite gate first: an authenticated Salesforce org, the Agentforce DX plugin installed, the DevOps Center org authenticated, and an identified pipeline. Write modes additionally require an identified pipeline stage. All calls target Salesforce API v67.0 minimum.
Will it change my org without asking?
No. Modes B–D must confirm before any write. Mode C requires a mandatory impact-preview table, Mode D re-presents the final test list (excluding rejected tests from the payload), and the API is never called until the user affirmatively approves.
Does it read my local repository for configuration?
No. It explicitly states that all DevOps Center data lives in the Salesforce org, not the local repo, and that the agent should always query the org with sf data query or sf api request rest rather than searching the filesystem.
Does it generate tests when coverage is missing?
No. In this version, when recommendation flags a new method with no suite coverage it directs the developer to author tests manually and points to separate skills for test generation and execution.
Install dx-devops-test-suite-assignments-configure
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
forcedotcom/sf-skills