staging-deployment-phase

Standard Operating Procedure for /ship-staging phase. Deploy feature to staging with auto-merge.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

This Claude skill provides a standardized, automated Standard Operating Procedure (SOP) for the staging deployment phase. It streamlines the transition from merged code to a live staging environment by orchestrating database migrations, health checks, and deployment reporting, ensuring a consistent and error-free release process.

Use Cases

  • Automating the deployment of newly merged features to staging environments to maintain a continuous delivery pipeline.
  • Executing and verifying database migrations automatically during the deployment process to ensure data consistency.
  • Performing post-deployment health checks to validate environment stability before handing off to QA teams.
  • Generating automated staging ship reports to provide stakeholders with clear visibility into deployment status and outcomes.
namestaging-deployment-phase
description"Standard Operating Procedure for /ship-staging phase. Deploy feature to staging with auto-merge."
allowed-toolsRead, Edit, Bash

Staging Deployment Phase: Standard Operating Procedure

Training Guide: Deploy feature to staging environment for validation.

Phase Overview

Purpose: Deploy to staging, run migrations, verify health Inputs: Merged PR, passing CI Outputs: Staging deployment, ship report Expected duration: 15-30 minutes

Execution Steps

  1. Verify PR merged to main
  2. Run database migrations (if any)
  3. Deploy to staging environment
  4. Run health checks
  5. Verify deployment successful
  6. Generate staging ship report

Common Mistakes

  • Deployment failures
  • Migration issues
  • Health check failures

Completion Criteria

  • Deployed to staging
  • Health checks pass
  • Ship report generated

This SOP guides staging deployment.