deploy

Build backend JARs, Docker images, and start containers for production deployment.

Updated Jun 10, 2025

Search Tags:#production #docker #deploy #ci-cd #health-check

Ready to run

npx skills add https://github.com/skrymer/trading --skill deploy-skrymer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/skrymer/trading/tree/main/.claude/skills/deploy
Command: npx skills add https://github.com/skrymer/trading --skill deploy-skrymer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The deployment process for the trading platform is manual and error-prone; this skill automates building, packaging, and deploying only services with changes, while performing health checks.

Core Features & Use Cases

Selective deployment: only builds and deploys services that changed since last commit.
Health verification: runs post-deploy health checks to confirm service readiness.
Version-aware: accepts optional version tags to pin specific component versions.

Quick Start

Execute the deploy-prd.fish script with any provided arguments to deploy only changed services.

Frequently Asked Questions about deploy

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

FAQPage Schema

How do I automate production deployment for Docker containers and only deploy changed services?▼

Automate production deployment by building backend JARs, Docker images, and starting containers. This skill selectively deploys only services with changes since the last commit, reducing manual errors and deployment time.

How do I verify service health across multiple environments after a production deployment?▼

Verify service health after production deployment by running post-deploy health checks across midgaard, udgaard, and asgaard environments to confirm service readiness and validate the deployment.

Can I pin specific component versions during a Docker production deployment?▼

Pin specific component versions during Docker production deployment by passing optional version tags as command-line arguments to the deployment script for versioned control.

What is the best way to selectively deploy only changed services to production?▼

Selectively deploy changed services by comparing against the last commit, building backend JARs and Docker images only for modified components, and starting their containers.

Does this deployment automation work with Fish shell scripts?▼

Yes, the deployment automation executes via a Fish shell script that accepts command-line arguments for selective service deployment and version flags.

What limitations exist when deploying to midgaard, udgaard, and asgaard environments?▼

Health verification is limited to midgaard, udgaard, and asgaard environments, and selective deployment is restricted to services with detected changes since the last commit.