'staging' 검색 결과

Check release readiness by reviewing tests, type checks, linting, builds, security findings, documentation, and environment settings. Get a report separating deployment blockers from warnings, plus action items and checks for post-deployment health and rollback preparation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking readiness before a production deployment
• Reviewing staging environment settings
• Adding release checks to CI/CD

Set up mirrord preview environments that run changed services in isolated Kubernetes pods. Configure traffic filters, share previews through HTTPS links, and connect previews to pull request workflows so teams can review changes using shared cluster dependencies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Start a preview of a changed service in a shared cluster
• Share a preview with reviewers through an HTTPS link
• Create and stop previews for each pull request

Coordinate the AWS DevOps Agent across multiple AgentSpaces from one Claude Code session — route questions to the right space (prod vs staging vs knowledge), query several spaces in parallel and synthesize, or compare findings across accounts. Use whenever the user has more than one AgentSpace configured, mentions multiple AWS accounts, or asks something like "check both prod and staging", "compare across accounts", or "ask the knowledge space".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure Apollo.io multi-environment setup. Use when setting up development, staging, and production environments, or managing multiple Apollo configurations. Trigger with phrases like "apollo environments", "apollo staging", "apollo dev prod", "apollo multi-tenant", "apollo env config".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure Claude API across dev, staging, and production environments with isolated keys, model routing, and spend controls per environment. Trigger with phrases like "anthropic environments", "claude multi-env", "anthropic staging setup", "claude dev vs prod config".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design isolated Algolia development, staging, preview, and production targets with explicit promotion rules. Use when environments share credentials or index names, or previews need bounded search data. Trigger with "Algolia environments", "Algolia staging setup", or "preview index".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions workflows on the staging branch of the babysitter repo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Triggers a Power Platform Pipeline deployment run for a Power Pages solution. Selects a target stage, validates the package, optionally configures deployment settings (environment variables, connection references), then deploys and polls for completion. Use when asked to: "deploy pipeline", "run pipeline", "trigger deployment", "deploy to staging", "deploy to production", "run power platform pipeline", "deploy solution via pipeline", "promote solution", "push to staging", "push to production".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate real estate, architecture, and interior design showcase video prompts for Seedance 2.0 on Higgsfield. Use whenever the user wants property tours, real estate listings, architecture showcases, interior design videos, home staging content, property marketing, virtual tours, construction reveals, or any real estate/architecture video. Triggers on: real estate, property, house, apartment, architecture, interior design, home tour, listing video, property marketing, virtual tour, building, construction, renovation, home staging, or any real estate/architecture video request. Use even for "make a video for my listing" or "showcase this property.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deploy funnelcake (api + relay) to ANY environment (production, staging, poc) on GKE via ArgoCD. Use when: (1) Deploying new funnelcake commits, (2) Building Docker images for GKE (amd64), (3) Running ClickHouse migrations, (4) Troubleshooting ImagePullBackOff errors, (5) Syncing staging/poc after production deployment. Covers complete workflow with PRE-FLIGHT CHECKLIST to prevent common deployment failures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Acts as a director and previs supervisor for film, video, and AI filmmaking. Turns scripts, prose, briefs, or existing image and video assets into production deliverables — subtext breakdown, beat sheet, director's book, blocking and staging, shot list with coverage, keyframe and storyboard prompts, image-to-video motion prompts, sound and dialogue plans, edit timelines, continuity bibles, and QC repair notes. Carries genre playbooks, a controlled prompt lexicon, a coded failure-diagnosis manual, and capability-first adapters for current video and image models. Optionally applies one named director's style lens — Spielberg, Hitchcock, Kubrick, Kurosawa, Scorsese, Fellini, Bergman, Tarkovsky, Wong Kar-wai, Nolan, Villeneuve, Fincher, Refn, Bi Gan, Zhang Yimou, Hou Hsiao-hsien, Park Chan-wook, Malick, Michael Mann, Coen Brothers. Use for shot planning, blocking, staging, camera movement, visual continuity, storyboard and keyframe design, prompt repair, "in the style of X" direction, and any AI video workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provider-independent real estate media production for listing photos, virtual staging, property videos, walkthrough reels, floor-plan explainers, neighborhood clips, renovation concepts, agent ads, and generated or retouched property visuals. Use when creating, editing, reviewing, prompting, packaging, or approving real estate marketing content where property truthfulness, listing/MLS compliance, fair-housing risk, staging disclosure, privacy, accessibility, platform variants, or real-estate QA matter.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design environment strategy for testing across dev, CI, preview, staging, and production — Docker Compose test infrastructure, multi-stage Dockerfiles, seed-data lifecycle, per-PR preview environments, production parity, and external-dependency stubbing at the HTTP boundary. Use when: "set up test environment," "docker-compose for tests," "per-PR preview environment," "staging parity," "spin up test infra," "environment tiers." Not for: choosing mock-vs-stub-vs-fake per dependency — use service-virtualization; factory and fixture data patterns — use test-data-management; pipeline/Actions config — use ci-cd-integration. Related: test-data-management, ci-cd-integration, contract-testing, service-virtualization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Internal — for Boundless team members only. Monitor Boundless deployment pipelines (AWS CodePipeline + CodeBuild) on the ops account. Use when the user wants to track a deployment after merging a PR, check whether a commit has rolled out to staging/prod, diagnose a failed deployment, watch the status of a specific pipeline, or get prompted to approve a production rollout once staging succeeds. Do NOT use for service runtime debugging (use ops-logs-query) or for deploying dev infrastructure (use ops-infra-deploy).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Internal — for Boundless team members only. Cross-reference Boundless indexer API data, broker telemetry, and service logs to investigate production and staging operational issues. Use when the user wants to understand why slashings happened on prod/staging, diagnose prover or service failures in deployed environments, correlate market events with broker behavior, investigate fulfillment rate drops, look at prover/service logs, or perform any analysis that requires combining on-chain indexer data with off-chain broker telemetry and CloudWatch logs. Also use when the user asks to "investigate", "diagnose", or "find root cause" for prover, service, or market issues on live networks. Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Инструкции для автора шаблона IWE: staging-канал (обкатка → FMT), авторские правила L3, Extensions Gate. Загружать при: staging / promote / author / шаблон / extensions / L3.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Register trained models in MLflow Model Registry with version control, implement stage transitions (Staging, Production, Archived) with approval workflows, and manage model lineage with comprehensive metadata and deployment tracking. Use when promoting a trained model from experimentation to production, managing multiple model versions across development stages, implementing approval workflows for governance, rolling back to previous versions, or auditing model changes for compliance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stage, commit, and amend changes with conventional commit messages. Covers reviewing changes, selective staging, writing descriptive commit messages using HEREDOC format, and verifying commit history. Use when saving a logical unit of work to version control, creating a commit with a conventional message, amending the most recent commit, or reviewing staged changes before committing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Day-to-day operation runbook for nuxt-crouton apps — boot any app/POC locally with auth working, seed and inspect the local database (including the miniflare-vs-.data split that makes seeded data "disappear"), turn on the review overlay / eruda, observe deployed staging (tail, smoke, row counts), and capture screenshots. Use when asked to "run the app", "boot velo/fanfare/a poc locally", "why can't I log in locally", "seed the database", "the seed data doesn't show up", "look at the local db", "check what's on staging", "screenshot the app", or "where do the artifacts land".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

exact-13 staging planを独立評価したいとき、4条件とdigestに束縛したplan-findings.jsonを生成したいときに使う。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manual testing + bug filing for Enterprise / SaaS products. Parses a Feishu test doc (scope + repo + bitable URL), observes staging via claude-in-chrome, captures DOM/console/network/screenshot evidence, then dual-tracks each finding — Feishu Bitable record (with attachments) + GitHub issue (<REPO>#<ISSUE_NUMBER> format — English-primary, Chinese collapsed, R2-hosted screenshots, matching type label). Enforces dedup across bitable + GitHub issues + PRs, and mandatory P0/P1/P2 priority prompt when unclear. Trigger whenever the user says "test and report", "test and report side-by-side", "start system testing", "experience staging", "collaborate on bug filing", "collect feedback", a shared Feishu testing doc, a bitable URL + finding, or any UX/bug needing both bitable + GitHub tracking. Do NOT use for writing product code, PR review, CI debugging, or general "how do I use this product" questions — those go to normal dev / PR-review / support flows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure Adobe OAuth credentials and API access across development, staging, and production environments with separate Developer Console projects, secret managers, and environment-specific scoping. Trigger with phrases like "adobe environments", "adobe staging", "adobe dev prod", "adobe environment setup", "adobe config by env".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automate Brex Staging tasks via Rube MCP (Composio). Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.