Deploy Light Bot to Production

Promotes a staging commit to production and deploys Light Bot via SSH, Git, Docker Compose, and env sync.

1|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/rrader/light-bot --skill deploy-light-bot-to-production
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Deploy Light Bot to Production
Source: https://github.com/rrader/light-bot/tree/main/.claude/skills/deploy-prod
Command: npx skills add https://github.com/rrader/light-bot --skill deploy-light-bot-to-production

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual, error-prone, and time-consuming process of deploying your Light Bot application to a production server. It streamlines complex Git operations, environment variable synchronization, and Docker commands into a single, reliable workflow.

Core Features & Use Cases

  • Automated Production Promotion: Seamlessly fast-forwards your prod branch to the latest stable staging commit.
  • Environment Variable Sync: Intelligently compares local .env.example with the production .env to identify and prompt for missing variables, preventing configuration drift.
  • One-Command Deployment: Executes SSH commands to pull the latest code, rebuild Docker images, and restart services on the production server.
  • Use Case: A development team needs to push a thoroughly tested feature from staging to the live production environment. This Skill ensures a consistent, automated, and verifiable deployment without manual SSH commands or risking configuration errors.

Quick Start

Deploy the Light Bot to production. Ensure the staging environment is stable and I have the necessary SSH keys.

Frequently Asked Questions about Deploy Light Bot to Production

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

FAQPage Schema
How do I automate production deployments for my Light Bot application?

Automate production deployments by promoting your staging commit to the prod branch, then executing a single workflow that pulls the latest code, rebuilds the Docker image, restarts the service via SSH, and verifies deployment status—eliminating manual Git and Docker commands.

Can I deploy to production without manual SSH commands and configuration drift?

Yes. This workflow handles SSH access, Git branch promotion, Docker Compose operations, and environment variable synchronization automatically, comparing your local .env.example against production .env to identify and prompt for missing variables before deployment.

What do I need to deploy Light Bot to production?

You need SSH key access to your production server, an SSH host address, the project directory path on the server, the Docker Compose service name, and a stable staging environment ready to promote to production.

How does environment variable synchronization prevent production configuration errors?

The workflow intelligently compares your .env.example template with the production .env file, identifies missing variables, and prompts you to provide them before deployment proceeds, preventing incomplete or mismatched configurations.

What happens during the staging-to-production promotion workflow?

The workflow fast-forwards your prod branch to the latest staging commit, pulls updated code on the production server via SSH, rebuilds the Docker image, restarts the service, and returns deployment status and logs for verification.

Related Skills