production-deployment-phase

Deploy validated staging builds to production with semantic versioning and health checks.

Updated Jan 5, 2026

Search Tags:#deployment automation #semantic versioning #health checks #production deployment #Git deployment

Ready to run

npx skills add https://github.com/Marcus-Mok-GH/Claude-code-conductor --skill production-deployment-phase-marcus-mok-gh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: production-deployment-phase
Source: https://github.com/Marcus-Mok-GH/Claude-code-conductor/tree/main/.claude/skills/production-deployment-phase
Command: npx skills add https://github.com/Marcus-Mok-GH/Claude-code-conductor --skill production-deployment-phase-marcus-mok-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex process of promoting validated staging builds to production, ensuring smooth and error-free deployment with version control and health checks.

Core Features & Use Cases

Semantic Versioning: Bump versions in package.json and create release tags with semantic versioning.
Health Checks: Run checks on endpoints, databases, and services to ensure operational status.
Deployment Automation: Trigger production deployment based on different models (Git push, GitHub Actions, Direct deployment).
Use Case: Ideal for developers and DevOps engineers who need to streamline the deployment process, ensuring that new features and bug fixes are smoothly transitioned from staging to production.

Quick Start

Use the production-deployment-phase skill to deploy the latest version to production by running /ship-prod.

Frequently Asked Questions about production-deployment-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate production deployment with semantic versioning and health checks?▼

Production deployment automation uses semantic versioning to bump package versions and runs health checks on endpoints and databases before promoting validated staging builds, ensuring error-free release tagging and operational status.

What is the best way to trigger a Git deployment to production?▼

Git deployment to production can be triggered through Git push, GitHub Actions, or direct deployment models, automating the release of validated staging builds while applying semantic versioning and release tagging.

Do I need Git repository access for automated production deployment?▼

Yes, automated production deployment requires Git repository access and deployment platform configuration to handle semantic versioning, release tagging, and health checks during the staging-to-production promotion process.

How does semantic versioning work during a production deployment?▼

Semantic versioning during production deployment bumps the version in package.json and creates a release tag, ensuring version control is maintained when new features and bug fixes transition from staging to production.

What health checks are run before promoting a staging build to production?▼

Health checks run on endpoints, databases, and services to verify operational status before promoting validated staging builds to production, ensuring the deployment is smooth and error-free.

Can I use deployment automation for both new features and bug fixes?▼

Yes, deployment automation is ideal for streamlining the transition of both new features and bug fixes from staging to production, using semantic versioning and health checks to ensure smooth releases.