测试与 QA

asc-submission-health

942testing-qa

Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.

rorkai

coreml

936testing-qa

在 iOS 应用中集成 Core ML 模型，实现设备端机器学习推理。涵盖模型加载（.mlmodel、.mlpackage、.mlmodelc）、使用自动生成类和 MLFeatureProvider 进行预测、计算单元配置（CPU、GPU、神经网络引擎）、MLTensor、VNCoreMLRequest、MLComputePlan、多模型流水线以及部署策略。适用于加载 Core ML 模型、进行预测、配置计算单元或分析模型性能的场景。

tipkit

936testing-qa

实现并审查 Apple TipKit 功能发现 UI，适用于 iOS 17+ 应用。在添加或审核应用内提示、上下文帮助、教练标记、Tip、TipView、popoverTip、规则、事件、操作、显示频率、测试覆盖、可重用提示标识符或 iOS 18+ 的 TipGroup 和 CloudKit 提示同步时使用；避免用于通用 SwiftUI 导航或提示展示之外的布局。

app-clips

936testing-qa

构建iOS App Clip，支持调用URL、App Clip Code、NFC、二维码、Safari横幅、地图、信息、目标设置、App Store Connect体验、大小/能力限制、NSUserActivity路由、SKOverlay推广、App Group/钥匙串交接、临时通知、位置确认以及完整应用迁移。在创建App Clip或配置App Clip调用、体验设置或完整应用交接时使用。

asc-cli-usage

934testing-qa

关于在此仓库中使用 asc CLI 的指南（标志、输出格式、分页、认证和命令发现）。当需要运行或设计 asc 命令或通过 CLI 与 App Store Connect 交互时使用。

rudrankriyam

asc-submission-health

934testing-qa

诊断 App Store 提交阻塞问题并使用 asc 操作审核健康状态，包括就绪验证、修复路由、状态监控、取消和重试决策。当验证失败、版本处于无效状态、审核状态不明确或卡住、或失败的提交需要修复并重试时使用。对于分阶段、上传、发布和提交执行，请使用 asc-release-flow。

rudrankriyam

debugging-instruments

932testing-qa

使用 LLDB、交互式内存图调试器和 Instruments 调试 iOS 应用并分析性能。适用于崩溃、循环引用检查、卡顿、构建失败以及通用的 CPU、内存、能耗或网络分析。如需 .memgraph 捕获、leaks CLI 所有权路径或持久堆增长，请使用 ios-memgraph-analysis；如需 ETTrace 捕获和 JSON，请使用 ios-ettrace-performance。

swift-language

932testing-qa

应用现代 Swift 语言模式与惯用法，适用于非并发、非 SwiftUI 的代码。涵盖 if/switch 表达式（Swift 5.9+）、类型化 throws（Swift 6+）、结果构建器、属性包装器、不透明类型与存在类型（some vs any）、guard 模式、Never 类型、正则构建器（Swift 5.7+）、基本 Codable 塑形（CodingKeys、自定义解码、嵌套容器）、现代集合 API（count(where:)、contains(where:)、replacing()）、基本 FormatStyle 用法以及字符串插值模式。在编写涉及泛型、协议、枚举、闭包或现代语言特性的核心 Swift 代码时使用；深度 Codable 路由至 swift-codable，详细格式化/本地化路由至 swift-formatstyle，API 命名路由至 swift-api-design-guidelines。

background-processing

932testing-qa

使用 BGTaskScheduler 在 iOS 上调度和执行后台工作。适用于注册 BGAppRefreshTask 进行短时后台获取、BGProcessingTask 进行长时间维护、BGContinuedProcessingTask（iOS 26+）进行前台启动并在后台继续的工作、后台 URLSession 下载或后台推送通知。涵盖 Info.plist 配置、过期处理、任务完成以及使用模拟启动进行调试。

ios-localization

在 iOS/macOS 应用中实现、审查或改进本地化和国际化——字符串目录 (.xcstrings)、生成的本地化符号、稳定的键命名、LocalizedStringKey、LocalizedStringResource、复数规则、数字/日期/测量的 FormatStyle、从右到左布局、动态类型以及区域感知格式化。适用于添加多语言支持、设置字符串目录、启用编译时安全的本地化键生成符号、处理复数形式、为不同区域格式化日期/数字/货币、测试本地化或使 UI 在阿拉伯语和希伯来语等 RTL 语言中正确显示。

swift-testing

Writes and migrates Swift Testing framework tests with @Test, @Suite, #expect, #require, confirmation, traits, withKnownIssue, Attachment.record, processExitsWith exit tests and capture lists, Test.cancel, Issue.record warnings/manual failures, XCTest-to-Swift Testing migration, Xcode 27 interoperability modes, XCUITest UI-test boundaries, performance/snapshot boundaries, mocking, async patterns, and test organization. Use when writing tests, converting XCTest assertions such as XCTUnwrap or XCTFail, reviewing advanced Swift Testing API availability, or deciding when to keep XCTest/XCUITest.

storekit

使用 StoreKit 2 实现、审查或改进应用内购买和订阅。适用于使用 SubscriptionStoreView 或 ProductView 构建付费墙、使用 Product 和 Transaction API 处理交易、验证权益、处理购买流程（消耗型、非消耗型、自动续期）、实现优惠码或促销/赢回/ introductory 优惠、管理订阅状态和续期状态、使用配置文件设置 StoreKit 测试，或集成家庭共享、请求购买、退款处理和账单重试逻辑。

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 技能。

iterate-pr

881testing-qa

迭代处理一个PR，直到可操作的CI通过且高/中优先级审查反馈被解决。用于PR CI失败、审查反馈或绿色检查循环；不等待人工批准、草稿状态或合并门禁。

getsentry

platform-metadata-deploy

788testing-qa

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).

omnistudio-integration-procedure-generate

788testing-qa

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).

omnistudio-flexcard-generate

788testing-qa

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).

omnistudio-datamapper-generate

786testing-qa

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).

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.

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).

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).

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.

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).