Diagnose and fix Swift strict-concurrency warnings in WooCommerce iOS. Use for Swift 6 migration, actor-isolation changes, and Sendable diagnostics in this repository.
日本語の概要は準備中です。原文の説明を表示しています。
8,392 件 ・ 関連度順
概要と使いどころ
Diagnose and fix Swift strict-concurrency warnings in WooCommerce iOS. Use for Swift 6 migration, actor-isolation changes, and Sendable diagnostics in this repository.
日本語の概要は準備中です。原文の説明を表示しています。
Run SwiftLint on the WooCommerce iOS project
日本語の概要は準備中です。原文の説明を表示しています。
Run tests for WooCommerce iOS (full suite or targeted)
日本語の概要は準備中です。原文の説明を表示しています。
Set up the ContextA8C MCP server for accessing Automattic internal resources (Slack, Linear, P2s, GitHub Enterprise, etc.)
日本語の概要は準備中です。原文の説明を表示しています。
Install dependencies and build tools for WooCommerce iOS
日本語の概要は準備中です。原文の説明を表示しています。
Create a pull request following WooCommerce iOS conventions
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes against WooCommerce iOS standards
日本語の概要は準備中です。原文の説明を表示しています。
Debug a failing test or build error in WooCommerce iOS
日本語の概要は準備中です。原文の説明を表示しています。
Provides parameterized testing patterns with JUnit 5, generates data-driven unit tests using @ParameterizedTest, @ValueSource, @CsvSource, @MethodSource. Creates tests that run the same logic with multiple input values. Use when writing data-driven Java tests, multiple test cases from single method, or boundary value analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize construction resource allocation across activities. Level resources, resolve over-allocations, and balance workload while minimizing schedule impact.
日本語の概要は準備中です。原文の説明を表示しています。
Calculate construction costs using resource-based method. Estimate project costs from work items, physical resource norms, and current prices.
日本語の概要は準備中です。原文の説明を表示しています。
Break down CWICR work items into component resources. Decompose aggregate items, analyze resource composition, and generate detailed bills of resources.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze construction resources (labor, materials, equipment) from DDC CWICR database. Calculate resource requirements, productivity metrics, and optimization recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize shared resource pools across multiple construction projects. Balance resource allocation, minimize conflicts, and maximize utilization across the portfolio.
日本語の概要は準備中です。原文の説明を表示しています。
Repair a failing WooCommerce Android Maestro flow by reproducing it against the store it runs on, inspecting Maestro selectors, patching the smallest selector/wait/setup issue, and rerunning with repeat evidence. Human-triggered only.
日本語の概要は準備中です。原文の説明を表示しています。
Provision a disposable Jurassic Ninja store for the Maestro smoke suite, connect Jetpack to the developer's own WordPress.com test account, create WooCommerce API keys, and write .maestro/.env.local. Use when Maestro setup is missing, when .env.local points at an expired store, or when a clean store is wanted.
日本語の概要は準備中です。原文の説明を表示しています。
Implements telehealth privacy compliance covering HIPAA requirements for virtual care, state licensing and recording consent laws, platform security with BAA requirements for telehealth vendors, cross-state prescribing rules, and OCR enforcement discretion during public health emergencies. Keywords: telehealth privacy, virtual care, HIPAA, recording consent, platform BAA, cross-state licensing, OCR enforcement.
日本語の概要は準備中です。原文の説明を表示しています。
Implements HIPAA minimum necessary standard under 45 CFR §164.502(b). Covers role-based access policies per workforce member category, routine vs non-routine disclosure protocols, reasonable reliance doctrine, documentation requirements, and HITECH amendments. Keywords: minimum necessary, role-based access, workforce, routine disclosure, HIPAA.
日本語の概要は準備中です。原文の説明を表示しています。
Implements HITECH Act privacy and security requirements including breach notification expansion, four-tier penalty structure, state attorney general enforcement authority, EHR meaningful use privacy conditions, and business associate direct liability. Keywords: HITECH Act, breach notification, penalty tiers, state AG enforcement, meaningful use, EHR privacy.
日本語の概要は準備中です。原文の説明を表示しています。
Implements HIPAA workforce training requirements under 45 CFR §164.530(b) (Privacy Rule) and 45 CFR §164.308(a)(5) (Security Rule). Covers initial onboarding training, periodic refresher cadence, role-based content differentiation, documentation of training completion, and sanction policy integration. Keywords: HIPAA training, workforce training, security awareness, privacy training, §164.530(b), §164.308(a)(5).
日本語の概要は準備中です。原文の説明を表示しています。
Develops data classification policies with tiered handling (public, internal, confidential, restricted), labeling requirements, enforcement mechanisms, and procedures per tier. Covers policy governance, exception handling, and compliance monitoring. Keywords: classification policy, data tiers, handling procedures, labeling, enforcement, data governance, information security.
日本語の概要は準備中です。原文の説明を表示しています。
Extract product data, prices, reviews, and seller information from any e-commerce platform using Apify's E-commerce Scraping Tool.
日本語の概要は準備中です。原文の説明を表示しています。
Owns repositories, data sources and mapping for Compose and Compose Multiplatform apps: DTO to domain to UiModel boundaries, Ktor clients and bearer auth, WebSocket and SSE, Room, DataStore, Paging 3, offline-first and data-layer tests. Use when writing or reviewing a repository, data source, DTO, mapper, HttpClient, bearer token, WebSocket, SSE, Room DAO, migration, DataStore, PagingSource, RemoteMediator, offline cache or MockEngine test. Do NOT use for ViewModel or UI wiring (compose-feature), composables (compose-ui), the MVI contract or error tiers (compose-architecture), Gradle modules (compose-project), or commonMain vs platform splits (compose-platform).
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end open source contribution workflow: from scanning issues to submitting PRs. Use this skill whenever the user wants to contribute to an open source project, find issues to fix, submit a pull request, fork a repo to contribute, fix a GitHub issue, or mentions 'open source contribution'. Also trigger when they provide a GitHub repo URL and ask about contributing, say things like 'help me submit a PR', 'find good first issues', 'I want to contribute to X', or mention fixing bugs in someone else's project.
日本語の概要は準備中です。原文の説明を表示しています。