「status」の検索結果

WooCommerce Memberships storage and relationship map for membership plan CPTs, user membership CPTs, post statuses, plan/user membership meta keys, rule storage, profile-field storage, order grant meta, and WooCommerce Subscriptions-linked memberships. Use when code reads or writes wc_membership_plan, wc_user_membership, wcm-* statuses, wc_memberships_rules, _subscription_id, _has_installment_plan, _free_trial_end_date, membership plan access meta, user membership dates, product/order grant meta, or when an agent needs exact Memberships CPT/meta names and the Memberships-Subscriptions relation.

日本語の概要は準備中です。原文の説明を表示しています。

Curated WooCommerce Subscriptions hook and extension-point map for choosing the right action/filter around WC_Subscription creation, status transitions, date changes, renewal orders, scheduled payments, payment retries, gateway events, switching, gifting, related orders, REST/API responses, and account/admin UI. Use when the user asks for a Woo Subscriptions hook list, "where should I hook", "after renewal", "subscription status changed", or when code contains WC_Subscription, wcs_create_subscription, wcs_create_renewal_order, woocommerce_scheduled_subscription_payment, wcs_renewal_order_created, payment_retry, wcs_get_subscriptions, wcsg_, subscription_switch, _subscription_switch_data, _recipient_user, wcsg_recipient, or subscription switching.

日本語の概要は準備中です。原文の説明を表示しています。

Curated WooCommerce Memberships hook and extension-point map for plugins that build on user memberships, membership plans, status transitions, purchase/free-signup grants, profile fields, REST API, webhooks, members-area templates, CSV import/export, and Woo Subscriptions-linked memberships. Use when the user asks for a Memberships hook list, "where should I hook", membership created/saved, status changed, grant access from order, user membership API, profile fields, member directory, or code contains wc_memberships_, WC_Memberships_User_Membership, WC_Memberships_Membership_Plan, wc_user_membership, wc_membership_plan, wcm-, _subscription_id, wc_memberships_rules, or woocommerce-memberships.

日本語の概要は準備中です。原文の説明を表示しています。

Customize WooCommerce transactional emails the classic PHP-template way (NOT the block email editor) — extend WC_Email, declare $id / $title / $template_html / $template_plain / $placeholders, hook trigger() to a woocommerce_order_status_*_notification action, register via the woocommerce_email_classes filter. Plus the canonical template-override pattern (copy templates/emails/*.php to your theme's /woocommerce/emails/ folder; wc_get_template resolves them automatically), and the get_default_subject / get_default_heading override pattern for admin-customizable strings. Use when adding a new transactional email (custom shipped notification, vendor split, internal alert), overriding an existing template, or customizing strings that the admin Settings cannot reach. Triggers on WC_Email, woocommerce_email_classes, woocommerce_order_status_*_notification, wc_get_template_html, template_html / template_plain in WC context, "transactional email" / "send WooCommerce email programmatically".

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Dagster — dagster data orchestration platform management. Covers asset management, pipeline runs, sensor and schedule status, IO manager configuration, partition management, and resource health. Use when checking asset materialization status, investigating run failures, managing schedules/sensors, or analyzing Dagster deployments.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Checkmk — checkmk infrastructure and application monitoring platform for hosts, services, network devices, and cloud resources. Covers host/service status, event console, rule management, agent deployment, and WATO configuration. Use when checking Checkmk monitoring status, investigating service problems, managing host configurations, or reviewing monitoring rules.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Circleci — circleCI pipeline and workflow management. Covers pipeline status, workflow analysis, job logs, credit usage monitoring, orb management, and project configuration. Use when checking CI status, investigating build failures, analyzing credit consumption, or managing CircleCI orbs.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Caprover — capRover self-hosted PaaS management covering app inventory, container status, custom domain mappings, persistent directory mounts, environment variable auditing, cluster node status, Docker registry integration, and Nginx configuration review. Use for managing CapRover infrastructure.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Buildkite — buildkite CI/CD pipeline and agent management. Covers build pipeline status, agent pool health, artifact management, build annotations, and cluster queue monitoring. Use when checking build status, investigating failures, managing agents, or reviewing pipeline configurations.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Cachet — cachet open-source status page management, component tracking, incident reporting, and metric visualization. Covers component group management, incident lifecycle, scheduled maintenance, metric points, and subscriber management. Use when managing self-hosted status pages, creating incidents, tracking component health, or reviewing uptime metrics in Cachet.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws Data Pipeline — aWS Data Pipeline workflow management and execution analysis. Covers pipeline inventory, pipeline definitions, execution status, object status, task runner health, and pipeline scheduling. Use when inspecting data pipeline health, debugging failed executions, reviewing pipeline definitions, or auditing pipeline schedules.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Argocd — argoCD GitOps continuous delivery management for Kubernetes. Covers application sync status, deployment health, rollback operations, repository management, cluster registration, RBAC analysis, and application diff review. Use when checking deployment status, investigating sync failures, managing GitOps applications, or auditing ArgoCD configurations.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Airbyte — airbyte data integration platform management. Covers connection status monitoring, sync job tracking, source and destination health, schema change detection, workspace management, and connector upgrades. Use when checking sync status, investigating job failures, managing Airbyte connections, or auditing data pipeline configurations.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Airflow — apache Airflow workflow orchestration management. Covers DAG management, task instance monitoring, executor health, pool status, variable management, connection audit, and scheduler diagnostics. Use when checking DAG run status, investigating task failures, managing Airflow resources, or auditing configurations.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws Config — aWS Config compliance dashboard, rule evaluation status, conformance pack management, and resource timeline analysis. Covers configuration recorder status, compliance summary, non-compliant resource investigation, remediation tracking, and aggregator management.

日本語の概要は準備中です。原文の説明を表示しています。

Cache dynamic and static responses on Netlify's CDN from Functions, Edge Functions, and proxies. Use when you add caching or cache-control headers to a function response, tune cache TTL or stale-while-revalidate, set up the durable cache, vary a cache key by query/header/cookie/country/language, purge or invalidate the cache by site or cache tag, use the programmatic Cache API (caches.open/match/put) or @netlify/cache helpers (fetchWithCache/cacheHeaders/getCacheStatus), speed up an expensive API call, add ISR or on-demand revalidation, or debug why a response is or isn't cached via the Cache-Status header.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Master orchestrator for the 5-step productivity loop. Runs audit, architect, analyst, refinery, and compounder in sequence or individually. Use when you want to run the full loop, start the system, check system status, resume from where you left off, or run a specific step. Manages state, sequencing, and skill chaining. Supports full loop, single step, resume, and status-only modes.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the product owner asks where the project stands, what to do next, or which phase of the Lean spec-driven pipeline is current — runs cradle status and proposes exactly one next step.

日本語の概要は準備中です。原文の説明を表示しています。

中断された組織を再開する。.state/org-state.md が存在し Status: SUSPENDED のとき、 「再開」「続きから」「前回どこまでやった？」と言われたときに使う。 起動時の自動ブリーフィングにも対応。

E-commerce product-management desk (Busabase App-in-Skill) for catalog master data, SKUs, pricing, inventory, channel status, content assets, compliance notes, lifecycle state, and approval-gated product operations. Use when the user invokes $kelly-products or /kelly-products, asks for 电商商品管理, 商品库, SKU 管理, inventory/reorder, product status across Amazon/Shopify/TikTok Shop/eBay, channel publishing approvals, price-change review, quality holds, product lifecycle/archive decisions, or a Busabase-backed product management desk.

日本語の概要は準備中です。原文の説明を表示しています。

Lightweight contract lifecycle management App-in-Skill (Busabase App-in-Skill) for contract inventory, lifecycle status, owners, obligations, renewal notices, and simple approval reminders. Use when the user invokes $kelly-clm or /kelly-clm, mentions CLM, contract lifecycle management, 合同管理, 合同台账, contract repository, obligation tracking, renewal reminders, notice deadlines, contract owners, signature readiness, or wants a simple UI to review contract status without doing detailed legal redlines.

日本語の概要は準備中です。原文の説明を表示しています。

GitHub repository management — triage PRs/issues, check Actions status, manage branch protection, tag releases, housekeeping (stale branches, stashes), CODEOWNERS, badges, and repo hardening. Use when the user asks about GitHub, PRs, CI/CD status, repo health, branch protection, releases, or any GitHub operations.

日本語の概要は準備中です。原文の説明を表示しています。

Implement damage, healing, status effects, alerts, movement modifiers, and timed gameplay effects consistently.

日本語の概要は準備中です。原文の説明を表示しています。