'rollback' 검색 결과

Generate an operational runbook template from a service name. Provide sections for starting, stopping, health checks, incident handling, maintenance, and rollback, so teams can add service-specific commands and build consistent operating procedures.

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

• Creating an initial runbook for a new service
• Standardizing incident procedures across teams
• Preparing documentation for on-call onboarding

Prepare a game's launch day patch by selecting known bugs that are safe to fix quickly. Coordinate minimal fixes, verify affected areas, and document deferred issues, quality checks, rollback procedures, and patch notes.

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

• Selecting known bugs for a launch day patch
• Planning minor fixes from platform certification feedback
• Verifying fixes and checking affected game systems

Prepare a deployment checklist covering tests, approvals, database changes, release steps, and monitoring. Tailor it to the release and document rollback triggers, the conditions for reverting a change, before production deployment begins.

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

• Prepare checks for an upcoming production release
• Review a release with database migrations
• Verify feature flags and CI status before deployment

Rehearse Convex schema changes on a deployment seeded with a production snapshot. Populate existing records, verify data and behavior, then repeat the proven sequence in production with explicit approval, keeping the snapshot available for rollback.

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

• Rehearse schema changes using a copy of production data
• Populate existing records before requiring a new field
• Verify migrated data and app behavior before production

Prepare and deploy Three.js or other web games from a tested commit, a specific saved code version. Check the live game's controls, assets, and display, then record release evidence and a rollback target.

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

• Releasing a tested web game
• Checking controls and assets in production
• Recording release evidence and a rollback target

Manage a project's stored materials through inventory, migration, archiving, and ranking based on verified source reads. Changes follow owner approval, preserve material references, and include validation records and rollback procedures.

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

• Inventory stored materials before migration
• Rank reading candidates using verified sources
• Archive materials while preserving references

Organize software releases on GitHub, from version suggestions and release notes to testing, builds, and deployment. Coordinate multiple packages or repositories, roll changes out in stages, and configure rollback to restore an earlier release when problems occur.

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

• Preparing version updates and release notes
• Coordinating releases across packages and repositories
• Deploying in stages with monitoring and rollback

Restore project files from a previous Git checkpoint after previewing affected files and receiving explicit confirmation. Create a safety tag before restoration, preserve recorded lessons, and keep the current branch and commit history in place.

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

• Listing available project checkpoints
• Restoring files after an unsuccessful change
• Previewing files affected by a rollback

Manage a project's stored materials through inventory, migration, archiving, and ranking based on verified source reads. Changes follow owner approval, preserve material references, and include validation records and rollback procedures.

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

• Inventory stored materials before migration
• Rank reading candidates using verified sources
• Archive materials while preserving references

Enhancement overlay — version the WHOLE deployable LLM-app artifact as one bundle: prompts + compiled programs + model snapshot pins + retrieval config + eval-set version, versioned together so a deploy is reproducible and rollback is atomic. Activate when preparing to deploy an LLM app, when asking "what exactly is running in prod right now?", when a deploy must be reproducible months later, or when an incident needs a clean rollback. The core reframe: an LLM app artifact is NOT an ML model — it is a manifest over many independently-mutable parts, not one weights file. Do NOT activate for one-off prompt edits with no deploy, for a single-component demo, or where a vendor owns the whole prompt lifecycle. For versioning ONE compiled prompt use [[agentsop-per-model-artifacts]]; for the CI comparison mechanism use [[agentsop-regression-gate]]. Search keywords: prompt versioning, reproducible deploy, what is running in prod, rollback LLM app, model pinning, prompt registry, version prompts and config.

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

Documents rollback procedures before making risky changes. Covers what's changing, verification steps, rollback procedures, and blast radius assessment. Use before database migrations, breaking API changes, infrastructure or DNS changes, large dependency upgrades, or any change where undo is not obvious.

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

Use when planning, reviewing, or troubleshooting Salesforce metadata releases and admin deployment processes. Triggers: 'change set', 'deployment plan', 'rollback', 'DevOps Center', 'SFDX deploy', 'release checklist', 'production deployment', 'validation only deploy', 'quick deploy', 'test level', 'rollbackOnError', 'destructive changes', 'package.xml for an admin release', 'deployment status'. NOT for change set upload mechanics — use devops/change-set-deployment. NOT for scoring release risk up front — use admin/deployment-risk-assessment.

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

Ensure design/ADR changes include a concrete migration plan, rollout strategy, rollback conditions, and compatibility considerations.

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

복잡한 작업과 실패에서 근본 원인, 다음에 취할 행동, 문제를 알아볼 징후를 추출해 재사용할 학습 기록으로 정리합니다. 원인이 같은 기존 기록과의 중복도 정리합니다.

• 복잡한 작업 후 배운 점 기록
• 장애 조사의 원인과 교훈 정리
• 근본 원인이 같은 학습 기록 통합

코드 변경 시 테스트, 타입 검사, 빌드를 자동 실행해 배포 전 품질 확인 절차를 마련합니다. GitHub Actions 설정부터 단계적 배포와 롤백 절차까지 다룹니다.

• 새 프로젝트에 CI 도입하기
• 테스트와 품질 검사 자동화하기
• 단계적 배포와 롤백 설계하기

코드와 에이전트 결과물을 검증하고 신뢰도를 점수로 확인합니다. 기준 미달 변경의 자동 되돌리기, 품질 추이 모니터링과 보고서 출력도 다룹니다.

• AI가 생성한 코드 검증하기
• 검증에 실패한 변경 되돌리기
• 시간에 따른 품질 변화 확인하기

Control a running iTerm2 workspace from the command line. See what each terminal pane is doing, send commands, read current and past output, arrange windows and tabs, manage tmux integration, and change preferences.

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

• See what is running in every terminal pane
• Send commands and read terminal output history
• Create and restore layouts with multiple panes

Control a running iTerm2 workspace from the command line. Inspect processes and directories across panes, send commands, read terminal history, arrange windows and tabs, and manage preferences or tmux integration.

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

• Check processes and directories across panes
• Send commands and read output history
• Create split panes and restore layouts

Plan AWS infrastructure changes by checking application requirements and existing configuration, then selecting guidance from an external skill collection. Produces a reviewable plan covering access permissions, networking, cost assumptions, validation, and rollback.

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

• Choosing an AWS architecture for an existing application
• Reviewing an infrastructure plan before deployment
• Planning changes with minimal access permissions

Improve an existing AI agent by analyzing execution records, user feedback, and performance metrics. Refine prompts and workflows, compare original and revised versions through tests, and plan staged releases with monitoring and rollback when results worsen.

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

• Investigating recurring agent failures and user corrections
• Refining prompts, examples, and output formats
• Comparing original and revised agents with A/B tests

Design machine learning workflows from data preparation through training, validation, deployment, and monitoring. Use templates and guidance to connect stages, track versions and experiments, handle failures, and plan gradual releases with rollback options.

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

• Designing an end-to-end machine learning pipeline
• Building reproducible training workflows
• Comparing models before production deployment

Helps plan and implement database structure changes and data transformations using Sequelize, TypeORM, or Prisma. Includes staged changes intended to avoid downtime, plus transaction and backup examples for rolling back failed migrations.

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

• Renaming database columns in stages
• Splitting stored addresses into separate fields
• Preparing rollback steps for failed migrations

Design CI/CD pipelines that move applications through development, staging, and production. Define approval and security checks, gradual release strategies, health checks, and rollback procedures, and investigate gates or deployments that fail to progress.

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

• Designing CI/CD pipelines across multiple environments
• Introducing canary or blue-green releases
• Investigating stalled approvals and release gates

Diagnose Fedora Linux problems with a structured troubleshooting plan. Get commands for checking services, logs, and packages, followed by remediation, validation, and rollback steps that account for SELinux and firewalld where relevant.

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

• Investigating a service that will not start
• Troubleshooting package-related problems
• Checking SELinux or firewall involvement