测试与 QA
测试、调试、验证和质量工作流
Skills 列表

storekit
使用 StoreKit 2 实现、审查或改进应用内购买和订阅。适用于使用 SubscriptionStoreView 或 ProductView 构建付费墙、使用 Product 和 Transaction API 处理交易、验证权益、处理购买流程(消耗型、非消耗型、自动续期)、实现优惠码或促销/赢回/ introductory 优惠、管理订阅状态和续期状态、使用配置文件设置 StoreKit 测试,或集成家庭共享、请求购买、退款处理和账单重试逻辑。
dpearson2699
apple-on-device-ai
在 iPhone、iPad 和 Mac 上使用 Foundation Models、Core ML、MLX Swift 或 llama.cpp 构建私密、设备端 AI 功能。适用于选择 Apple 本地模型运行时、构建 Apple Intelligence 聊天机器人或工具调用功能、在 Apple Silicon 上运行 LLM、将 Python 模型转换或压缩为 Core ML,或比较设备端推理后端。对于 Swift Core ML 加载和预测代码,请使用 coreml 技能。
dpearson2699
iterate-pr
迭代处理一个PR,直到可操作的CI通过且高/中优先级审查反馈被解决。用于PR CI失败、审查反馈或绿色检查循环;不等待人工批准、草稿状态或合并门禁。
getsentry
terraform-policy
Write, test, or convert Terraform Policy files (.policy.hcl, .policytest.hcl, Sentinel→tfpolicy). Triggers: policy.hcl, policytest, convert sentinel, tfpolicy, write a policy.
hashicorp
dx-code-analyzer-custom-rule-create
Create custom Code Analyzer rules for Regex (pattern matching), PMD (XPath/AST for Apex and metadata XML), and ESLint (LWC/JavaScript/TypeScript). Use when users want to enforce coding standards, ban patterns, detect hardcoded values, govern metadata, or add rules not in the built-in set. TRIGGER when: user says 'create a rule', 'ban System.debug', 'enforce naming convention', 'detect hardcoded IDs', 'custom rule', 'xpath rule', 'regex rule', 'add a PMD rule', 'enforce a policy', 'create a check for', 'flag this pattern', 'make a rule that catches', 'metadata rule', 'check permissions', 'enforce API version', 'eslint rule', 'lwc rule', 'override rule threshold', 'customize complexity', or describes a pattern to enforce. DO NOT TRIGGER when: user wants to run a scan (use dx-code-analyzer-run), configure engines (use dx-code-analyzer-configure), or explain existing rules (use dx-code-analyzer-run).
forcedotcom
connecting-datacloud
Salesforce Data Cloud Connect phase. Use this skill when the user manages Data Cloud connections, connectors, or sets up a new source system. TRIGGER when: user manages Data Cloud connections, connectors, connector metadata, tests a connection, browses source objects or databases, or sets up a new source system. DO NOT TRIGGER when: the task is about data streams or DLOs (use preparing-datacloud), DMOs or identity resolution (use harmonizing-datacloud), retrieval/search (use retrieving-datacloud), or STDM telemetry (use observing-agentforce).
forcedotcom
platform-metadata-deploy
Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex code (use platform-apex-generate), building LWC components (use experience-lwc-generate), creating metadata definitions (use platform-custom-object-generate or platform-custom-field-generate), or querying org data (use platform-data-manage).
forcedotcom
omnistudio-integration-procedure-generate
OmniStudio Integration Procedure creation and validation with 110-point scoring. Use this skill when building server-side process orchestrations that combine Data Mapper actions, Apex Remote Actions, HTTP callouts, and conditional logic. TRIGGER when: user creates Integration Procedures, adds Data Mapper steps, configures Remote Actions, or reviews existing IP configurations. DO NOT TRIGGER when: building OmniScripts (use omnistudio-omniscript-generate), creating Data Mappers directly (use omnistudio-datamapper-generate), or analyzing cross-component dependencies (use omnistudio-dependencies-analyze).
forcedotcom
omnistudio-flexcard-generate
OmniStudio FlexCard creation and validation with 130-point scoring. Use when building at-a-glance UI cards, configuring data source bindings to Integration Procedures, or reviewing existing FlexCard definitions for accessibility and performance. TRIGGER when: user creates FlexCards, configures data sources, designs card layouts, or asks about OmniUiCard metadata. DO NOT TRIGGER when: building OmniScripts (use omnistudio-omniscript-generate), creating Integration Procedures (use omnistudio-integration-procedure-generate), or analyzing dependencies (use omnistudio-dependencies-analyze).
forcedotcom
omnistudio-datamapper-generate
OmniStudio Data Mapper (formerly DataRaptor) creation and validation with 100-point scoring. Use when building Extract, Transform, Load, or Turbo Extract Data Mappers, mapping Salesforce object fields, or reviewing existing Data Mapper configurations. TRIGGER when: user creates Data Mappers, configures field mappings, works with OmniDataTransform metadata, or asks about DataRaptor/Data Mapper patterns. DO NOT TRIGGER when: building Integration Procedures (use omnistudio-integration-procedure-generate), authoring OmniScripts (use omnistudio-omniscript-generate), or analyzing cross-component dependencies (use omnistudio-dependencies-analyze).
forcedotcom
developing-agentforce
Build, modify, debug, and deploy agents with Agentforce Agent Script. TRIGGER when: user creates, modifies, or asks about .agent files or aiAuthoringBundle metadata; changes agent behavior, responses, or conversation logic; designs agent actions, tools, subagents, or flow control; writes or reviews an Agent Spec; previews, debugs, deploys, publishes, or tests agents; uses Agent Script CLI commands (sf agent generate/preview/publish/test). DO NOT TRIGGER when: Apex development, Flow building, Prompt Template authoring, Experience Cloud configuration, or general Salesforce CLI tasks unrelated to Agent Script.
forcedotcom
experience-ui-bundle-app-coordinate
MUST activate when the user wants to build, create, or generate a React application, React app, web application, single-page application (SPA), or frontend application — even if no project files exist yet. MUST also activate when the project contains a uiBundles/*/src/ directory or sfdx-project.json and the prompt says create, build, construct, or generate a new app, site, or page from scratch — even if the prompt also describes visual styling. MUST also activate when the task spans more than one ui-bundle skill. Use this skill when building a complete app end-to-end. Do NOT use for Lightning Experience apps with custom objects (use platform-lightning-app-coordinate). Do NOT use for single-concern edits to an existing page (use experience-ui-bundle-frontend-generate).
forcedotcom
dx-devops-test-failures-analyze
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).
forcedotcom
dx-devops-test-pipeline-configure
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.
forcedotcom
dx-devops-test-suite-run
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).
forcedotcom
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 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).
forcedotcom
dx-code-analyzer-configure
Set up, configure, and troubleshoot Salesforce Code Analyzer for any project. Handles installation, prerequisite checks, diagnosing broken setups, creating and editing code-analyzer.yml overrides, engine-specific settings, ignore patterns, severity overrides, and CI/CD pipeline setup. TRIGGER when: user says 'set up code analyzer', 'configure code analyzer', 'install code analyzer', 'code analyzer not working', 'fix my setup', 'scan failing', 'check my setup', 'enable/disable engine', 'exclude files', 'change severity', 'set up GitHub Actions', 'set up CI/CD', 'add to pipeline', 'pipeline fail', 'update my workflow', 'quality gate', 'fail on violations', 'scan changed files only', 'add SARIF', 'code-analyzer.yml', 'ESLint config', 'increase SFGE memory', or reports errors running Code Analyzer. DO NOT TRIGGER when: user wants to run a scan (use dx-code-analyzer-run), fix violations, explain rules, create custom rules (use dx-code-analyzer-custom-rule-create), or suppress violations.
forcedotcom
agentforce-generate
Build, modify, optimize, debug, and deploy agents with Agentforce Agent Script. TRIGGER when: user creates, modifies, optimizes, or asks about .agent files or aiAuthoringBundle metadata; changes agent behavior, responses, or conversation logic; designs agent actions, tools, subagents, or flow control; writes or reviews an Agent Spec; wants to optimize, improve, or refactor an agent; previews, debugs, deploys, publishes, or tests agents; uses Agent Script CLI commands (sf agent generate/preview/publish/test); registers/creates/lists/updates/deletes MCP servers, whitelists/approves MCP tools, fetches MCP assets, or configures MCP authentication (sf agent mcp). DO NOT TRIGGER when: Apex development, Flow building, Prompt Template authoring, Experience Cloud configuration, or general Salesforce CLI tasks unrelated to Agent Script.
forcedotcom
agentforce-test
Write, run, and analyze structured test suites for Agentforce agents — functional AND security. TRIGGER when: user writes or modifies test spec YAML (AiEvaluationDefinition); runs sf agent test create, run, run-eval, or results commands; asks about test coverage strategy, metric selection, or custom evaluations; interprets test results or diagnoses test failures; asks about batch testing, regression suites, or CI/CD test integration; requests security testing, OWASP LLM Top 10, red-teaming, penetration testing, prompt-injection tests, a security grade, or a vulnerability assessment of an agent. DO NOT TRIGGER when: user creates, modifies, previews, or debugs .agent files (use agentforce-generate); deploys or publishes agents; writes Agent Script code; uses sf agent preview for development iteration; analyzes production session traces (use agentforce-observe); performs a static safety review of .agent file content (use agentforce-generate Section 15).
forcedotcom
platform-metadata-api-context-get
Salesforce 元数据生成的必需配套技能——在加载任何元数据生成技能的同一轮中,同时加载此模式/API 上下文技能;如果你加载了生成器,也必须加载此技能。在创建、生成、添加、编辑或编写元数据或 *-meta.xml 文件时使用它:自定义对象、自定义字段、公式字段、选项列表、查找关系、主从关系、验证规则、权限集、配置文件、自定义选项卡、Lightning 记录页面、flexipage、列表视图、自定义应用程序、流程、布局、记录类型、共享规则、报表以及 604 种 Metadata API 类型。它提供权威的模式、字段、字段属性、必需标志、允许的枚举值和 XML 结构,确保生成的 *-meta.xml 能顺利部署——跳过它会导致元素名称幻觉和部署失败。触发条件:*-meta.xml、元数据模式、API 上下文、'Salesforce metadata' 或 'sfdx project'。不要用于 SOQL、DML、运行时 sObject 访问或 Tooling API 记录。
forcedotcom
platform-soql-query
SOQL 查询生成、优化和分析,采用 100 分评分。当用户需要编写或优化 SOQL/SOSL 时使用此技能:自然语言转查询生成、关系查询、聚合、查询计划分析以及 Salesforce 查询的性能或安全性改进。触发条件:用户编写、优化或调试 SOQL/SOSL 查询,处理 .soql 文件,或询问关系查询、聚合或查询性能。不触发:批量数据操作(使用 platform-data-manage)、Apex DML 逻辑(使用 platform-apex-generate)或报表/仪表板查询。
forcedotcom
platform-lightning-app-coordinate
根据自然语言描述构建完整的 Salesforce Lightning Experience 应用程序。当用户请求“完整应用”、“Lightning 应用”、“业务解决方案”、“管理系统”或描述需要多个相互关联的 Salesforce 组件(对象、字段、页面、选项卡、安全性)的场景时,使用此技能。按正确的依赖顺序编排所有必需的元数据类型,以生成可部署的应用程序。
forcedotcom
handling-sf-data
Salesforce 数据操作,采用 130 分评分。使用此技能可通过 sf CLI 和匿名 Apex 创建、更新、删除、批量导入/导出、生成测试数据以及清理组织记录。触发条件:用户创建测试数据、执行批量导入/导出、使用 sf data CLI 命令、需要用于 Apex 测试的数据工厂模式,或需要在 Salesforce 组织中填充/清理记录。不触发条件:仅编写 SOQL 查询(使用 querying-soql)、执行 Apex 测试(使用 running-apex-tests)或元数据部署(使用 deploying-metadata)。
forcedotcom
platform-apex-generate
主要的 Apex 编写技能,用于类生成、重构和审查。当用户提到 Apex、.cls、触发器,或要求创建/重构类(服务、选择器、领域、批处理、可排队、可调度、可调用、DTO、工具类、接口、抽象类、异常、REST 资源)时,始终激活。此技能适用于涉及 SObject CRUD、集合映射、获取相关记录、计划作业、批处理作业、触发器设计、@AuraEnabled 控制器、@RestResource 端点、自定义 REST API 或现有 Apex 代码审查的请求。
forcedotcom