「staging」の検索結果

Run the local pre-commit gate for the memex repo before staging a commit: format check, clippy with warnings denied, and the workspace unit-test suite, mirroring memex's own CI. Use right before `commit-changes` on a memex working tree, after editing any Rust crate under `crates/`, or when reproducing a red CI run locally. Optionally runs the Postgres-gated integration suite when the `memex-pg` container is up and `.env` is sourced. This is a verification gate, NOT a replacement for memex CI — CI remains the authority; this catches failures earlier.

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

Deploy applications to Kubernetes clusters using kubectl manifests for Deployments, Services, ConfigMaps, Secrets, and Ingress resources. Implement health checks, resource limits, rolling updates, and Helm chart packaging for production deployments. Use when deploying new applications to EKS, GKE, AKS, or self-hosted clusters, migrating from Docker Compose to container orchestration, implementing zero-downtime rolling updates, or setting up multi-environment deployments across dev, staging, and production.

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

Execute git commits using the Conventional Commits specification. Use this skill whenever the user says "commit", "git commit", "/commit", "stage and commit", "make a commit", "save my changes", or asks to commit specific files or all changes. Also triggers on phrases like "push my changes" (commit first), "commit everything", "commit with message X", or whenever git diff/status suggests uncommitted work the user wants to save. Handles auto-staging, diff analysis, message generation, breaking change detection, batch splitting of unrelated changes, safe pushes, and pre-commit hook failures gracefully. Always use this skill rather than ad-hoc git commit commands.

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

Use this skill when committing VCSDD pipeline artifacts to git. Provides conventional commit message format, phase tag patterns, and atomic staging strategies.

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

Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

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

Use when preparing or publishing a local project as a clean GitHub repository. Covers new repositories, private staging releases, public README cleanup, updates to existing remotes, and research-code packaging without datasets, checkpoints, papers, or generated artifacts.

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

How every delivered app ships and stays up — Cloudflare-first hosting, prod-only (no staging), the deploy→prod-verify loop, atomic deploy + rollback.

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

Review what Prisma Next migrations will run on merge or deploy, render the migration graph, resolve concurrent / diamond-convergence conflicts, and configure environment refs for CI. Use for "what migrations are going to run", "what runs on deploy", merge conflict, diamond convergence, concurrent migrations, migration status, ref management, staging, production, MIGRATION.DIVERGED, MIGRATION.NO_MARKER, MIGRATION.MARKER_NOT_IN_HISTORY, prisma migrate status, prisma migrate diff, prisma migrate resolve.

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

Tracks adversary C2 and staging infrastructure by clustering indicators on shared attributes (TLS/JARM, certificate fields, favicon hashes, ASN, registration patterns) to find related hosts. Activates for requests to track adversary infrastructure, cluster C2 servers, or pivot on infrastructure attributes to find related hosts.

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

Analyzes loader and dropper samples by identifying staging behavior — embedded or downloaded next-stage payloads, decode/decrypt routines, and the execution mechanism used to run the next stage. Activates for requests to analyze a loader or dropper, find a staged payload, or map multi-stage delivery behavior.

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

Use when a task needs the judgment of a dermatologist — triaging a pigmented lesion for melanoma risk, choosing a biopsy technique and reading the pathology in clinical context, staging a skin cancer to decide margins or Mohs referral, escalating psoriasis/eczema treatment by severity score, or managing isotretinoin risk under REMS/iPLEDGE rules.

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

Use when a task needs the judgment of a dental hygienist — full-mouth periodontal charting and staging, sequencing scaling and root planing across quadrants, deciding whether a finding needs escalation back to the dentist, or building a home-care compliance plan for a patient with active periodontal disease.

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

Use when a task needs the judgment of a construction laborer — determining which OSHA-mandated protective system (sloping, benching, shoring, or shielding) a trench needs given its soil classification and depth, working as spotter/signal person on a crane or heavy-equipment lift, staging material and equipment on an active multi-trade site, or reading which hazard zone (excavation, crane swing, electrical rough-in) is live as work moves across the site.

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

Use when a task needs the judgment of a carpenter's helper — cutting and staging lumber to a carpenter's layout marks, assembling and standing framed wall panels, running a material take-off and waste calculation for a framing package, or recognizing when a jobsite condition (a missing guardrail component, a nail-gun trigger setting, a header that doesn't match the plan) is a stop rather than a workaround.

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

Use when a task needs the judgment of a choreographer — building and teaching a dance number against a rehearsal-hour budget, staging repertory under a trust/estate's licensing rules, planning a tech-week spacing and cueing schedule, or diagnosing why a piece isn't reading from the audience.

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

Use when a task needs the judgment of a Bridge and Lock Tender — deciding whether to open a movable span for a vessel signal during a restricted-hours window, sequencing a lock chamber's fill/empty and valve staging, verifying an interlock/gate cycle before commanding span movement, resolving a marine-traffic-vs-vehicle-traffic conflict, or coordinating a vessel passage over VHF.

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

Use when a task needs the judgment of an aircraft service attendant — servicing an aircraft's potable water or lavatory/waste system without cross-connecting the two, sequencing turnaround tasks inside a fixed gate-time window, staging ground support equipment around an active aircraft, or timing servicing against a deicing/anti-icing holdover-time window before pushback.

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

Playwright-first strategy for shared DB + shared test accounts. Use when E2E tests collide in QA/staging, need safe parallelism, or require deterministic cleanup without touching baseline data. Covers per-test ownership, namespacing, ID-based teardown, serial shared-state suites, and optional stale-data janitor jobs.

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

Audit an emergency resource management system for crisis readiness. Evaluates inventory tracking accuracy, deployment request-to-arrival pipeline, logistics and route optimization, supply chain resilience, inter-agency resource sharing (NIMS/EDXL), staging area management.

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

Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl. Use when the user has an existing AI inference workload (on Cloud Run, the Gemini API, Gemini Enterprise Agent Platform, or a custom VM) and wants to move it to self-hosted inference on GKE, or asks follow-up questions during such a migration (hardware sizing, model staging, manifest generation, validation, traffic cutover). DO NOT use for brand new GKE inference deployments with no existing workload to migrate (use gke-inference instead). DO NOT use if the user intends to automate the migration via the Gemini Cloud Assist MCP server.

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

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

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

Detects review-blocking configuration issues including sub-1.0 version numbers, beta in app name, staging endpoints, and missing demo credentials that prevent reviewers from evaluating the app, violating Guidelines 2.1 and 2.3.

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

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

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

Implements one numbered sub-task from a task list at .ai/[feature]/tasks.md, running linters and tests, without staging, committing, or marking the task complete. Use when asked to carry out a specific sub-task by number, or as the inner step of a larger loop that handles commits separately. For the full loop including commits, use task-orchestration.

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