deploy

Automate verified software deployment with pre-flight checks and live validation.

Updated May 24, 2026
One-click install
npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill deploy-rcsnyder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/RCSnyder/lights-out-swe-plugin/tree/main/skills/deploy
Command: npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill deploy-rcsnyder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams push verified software to the intended deployment target without skipping critical access checks, rollback planning, or post-deploy validation.

Core Features & Use Cases

  • Pre-flight gatekeeping: Verifies deploy tooling, authentication, required config/secrets, and a successful build before any deployment attempt.
  • Rollback-first delivery: Forces the author to identify a specific rollback command and include incident response guidance in DELIVERY.md.
  • Post-deploy verification & client handoff: Confirms the deployed app is reachable/working and writes README.md plus a structured DELIVERY.md handoff document.
  • Use case: Deploy a freshly built web app to GitHub Pages or a Docker/VPS target while producing evidence of gate results and a client-ready delivery document.

Quick Start

Ask the agent to run the deploy phase for the current project, ensuring pre-flight checks pass and producing README.md and DELIVERY.md with verified access evidence.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I automate software deployment to GitHub Pages or a Docker VPS while enforcing pre-flight checks?

Automated deployment executes pre-flight access and configuration checks, performs the rollout to targets like GitHub Pages or Docker VPS, and validates live availability. It stops immediately on failed gates to ensure verified software delivery.

What is rollback-first delivery and how does it work for release verification?

Rollback-first delivery forces you to identify a specific rollback command and include incident response guidance in DELIVERY.md before deploying. This ensures safe release verification by requiring an explicit recovery plan.

Can I use CI/CD pipelines to push container images to a registry and verify the deployment?

Yes, CI/CD pipelines can automate container registry image pushes and scheduled cron setups. Post-deploy verification confirms the deployed application is reachable, logging evidence while writing README and DELIVERY artifacts.

Do I need to document a manual rollback plan before deploying over SSH or CI?

Yes, you must document an explicit rollback command and incident-response plan in DELIVERY.md before any SSH or CI rollout. Pre-flight gatekeeping verifies deploy tooling, authentication, and required secrets to stop on failed gates.

What's the best way to ensure safe delivery of a web app to Docker or VPS targets?

Safe delivery requires pre-flight checks for access and configuration, a successful build, and a documented rollback command. Post-deploy verification then confirms the app is reachable and writes a structured DELIVERY.md handoff document.

Why does my deployment fail when access controls or configuration checks are missing?

Deployments fail on missing access controls because pre-flight gatekeeping verifies authentication, required config, and secrets before any attempt. This stop-on-failed-gates mechanism prevents unverified software from reaching production targets.