production-deployment-phase

Promote validated staging deployments to production with semantic versioning and health checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/marcusgoll/robinhood-algo-trading-bot --skill production-deployment-phase
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: production-deployment-phase
Source: https://github.com/marcusgoll/robinhood-algo-trading-bot/tree/main/.claude/skills/production-deployment-phase
Command: npx skills add https://github.com/marcusgoll/robinhood-algo-trading-bot --skill production-deployment-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes references (resource) components.

What problem does it solve?

This Skill eliminates the risks associated with manual, error-prone production deployments, such as downtime, incidents, and inconsistent releases.

Core Features & Use Cases

  • Automated Promotion: Guides the automated promotion of validated staging deployments to production.
  • Versioning & Release Tagging: Ensures proper semantic version bumping and creation of Git release tags for clear release history.
  • Health Checks & Monitoring: Verifies system health post-deployment and ensures monitoring is configured to catch issues early.
  • Use Case: After a feature has been thoroughly validated on staging, use this Skill to automate its promotion to production. This includes bumping the version, deploying the code, running health checks, creating a Git release tag, and configuring post-deploy monitoring to ensure a smooth, confident release.

Quick Start

1. Verify staging validation is complete

2. Bump the version using semantic versioning (e.g., npm version patch)

3. Deploy the validated build to your production environment

4. Run health checks to ensure all services are operational

5. Create a git release tag (e.g., git tag -a v1.0.0 -m "Release v1.0.0")

6. Generate a production ship report

7. Monitor the deployment for any post-release issues

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 deployments from staging?▼

Automate production deployments by promoting validated staging builds through CI/CD pipelines that handle versioning, health checks, and release tagging. This eliminates manual steps and reduces deployment errors and downtime risks.

What's the best way to manage semantic versioning and git release tags in CI/CD?▼

Semantic versioning in CI/CD pipelines bumps version numbers automatically based on changes, then creates git release tags to document each production release. This maintains clear release history and enables rollback if needed.

How do I verify a production deployment is healthy after release?▼

Run automated health checks post-deployment to confirm all services are operational, then configure monitoring to catch issues early. This verification step ensures stability before marking a release complete.

Can I use git tags to track production releases automatically?▼

Yes. Git release tags created automatically during deployment serve as immutable checkpoints for each production version, enabling clear release history tracking and facilitating quick identification of specific releases.

What should happen after a production deployment completes?▼

After deployment, generate a production ship report documenting the release, monitor for post-release issues, and keep health checks active. This post-deploy phase confirms stability and provides audit records for compliance.