428 skills · sorted by relevance
Roll back Kortix production to a previously released version using existing builds. Covers frontend and backend rollback, database compatibility checks, prevention of unintended frontend rebuilds, and returning to the latest version through a later release.
Use before and after calling rollback_release - what a rollback restores per delivery mode, when a schema change makes a code rollback unsafe, how to work and report manual_steps, and what to do when rollback_release refuses
The English summary is being prepared. Showing the original description.
Creates safe rollback procedures for deployments with automated workflows, rollback runbooks, version management, and incident response. Use for "rollback automation", "deployment recovery", "incident response", or "production rollback".
The English summary is being prepared. Showing the original description.
Prepare a structured request for a system or process change, covering business reasons, affected users, risks, implementation steps, stakeholder communications, required approvals, and a rollback plan that explains how to reverse the change.
Plan database, service, and infrastructure migrations with phased steps, compatibility checks, and rollback procedures for returning to the previous system. Define risks and validation checkpoints to guide transitions with minimal disruption to business operations.
Suggests rollback strategies for failed deployments across different platforms and failure types. Use when deployments fail and need to be reverted, including application code rollbacks, database migration reversions, infrastructure changes, and configuration updates. Supports Docker/Docker Compose environments with step-by-step procedural guidance for safe and effective rollback execution.
The English summary is being prepared. Showing the original description.
Use when a practitioner needs to classify the risk level of an upcoming Salesforce deployment, define rollback trigger conditions, or assign decision authority before the release window opens. Triggers: 'how risky is this release', 'what needs rollback planning', 'classify deployment risk', 'pre-deployment risk checklist', 'rollback decision authority', 'high risk metadata types'. NOT for executing the deployment itself, writing CI/CD pipeline code, or troubleshooting failures after a deployment has already run — use admin/change-management-and-deployment for execution planning and devops/deployment-error-troubleshooting for post-failure diagnosis.
The English summary is being prepared. Showing the original description.
Prepare web applications for production with Docker configurations, automated testing and deployment workflows, health checks, and rollback plans. Compare release strategies and review application, infrastructure, monitoring, security, and operational readiness before launch.
Plan and review machine learning systems for production use, covering data requirements, repeatable training, quality checks, deployment, monitoring, and rollback. Produce concrete plans and review findings for moving model experiments into operational systems.
Helps prepare web applications for production with automated testing and deployment workflows, Docker packaging, health checks, and rollback plans. Provides examples and checklists for choosing release strategies and reviewing readiness before launch.
Manage continuously running or cloud-hosted agents with lifecycle controls, logs, metrics, restricted permissions, and emergency stops. It guides incident response, staged deployments, rollbacks, and tracking success rates and cost per successful task.
Plan and implement migrations for data, APIs, configuration, and dependencies while preserving existing data and compatibility. Define rollback steps, check old and new behavior, and handle retries and partial failures during staged transitions.
Prepare a production release with checks for code quality, security, performance, accessibility, and infrastructure. Plan monitoring, gradual feature exposure, and rollback steps, then use release metrics and reliability limits to guide rollout decisions.
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.
Review pending database migration SQL before applying schema changes. Check references between tables, rollback coverage, required defaults, destructive operations, and naming conventions, then report errors, warnings, and suggestions with file paths and line numbers.
Coordinate software releases on GitHub, from version updates and release notes to testing, builds, deployment, and rollback. It describes workflows using multiple AI agents, including coordinated package releases and gradual deployments with monitoring.
Review database migration files before merging changes. It gathers evidence about what the changes do, rollback limits, database locks, and risks from large data volumes, then reports blockers when evidence needed for a decision is missing.
Guide production incident handling by establishing impact, start time, and recent changes before proposing action. Document evidence for rollback requests, keep the issue updated, and distinguish service recovery from resolution that explains the incident.
Design and review infrastructure and release workflows with checks tailored to the environment. Covers automated build and deployment pipelines, containers, health checks, rollback plans, feature flags, and mobile releases to help assess readiness before deployment.
Create rollout plans for application and infrastructure changes. Organize readiness checks, deployment steps, health indicators, rollback procedures, and stakeholder communications, adapting the detail to the target environment, change type, and level of risk.
Plan and implement database structure changes and data transfers using Sequelize, TypeORM, or Prisma. Covers staged changes to keep services running, rollback procedures to undo changes, backups, and migration verification.
Create or update step-by-step instructions for recurring operational tasks. Document exact commands, expected results, failure responses, verification checks, rollback steps, and escalation contacts so operations teams have a concrete procedure to follow.
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.
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.