debug-vps-deployment

Debug production VPS deployments and resolve OtterStack failures until services are healthy.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/jayteealao/Aperture --skill debug-vps-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-vps-deployment
Source: https://github.com/jayteealao/Aperture/tree/main/.claude/skills/debug-vps-deployment
Command: npx skills add https://github.com/jayteealao/Aperture --skill debug-vps-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploys to the production VPS ([email protected]) and iteratively debug OtterStack deployments until successful, enabling rapid resolution of deployment issues.

Core Features & Use Cases

  • Iterative debugging loop: Connects to a VPS, triggers OtterStack deployments, captures errors, and applies fixes until health checks pass.
  • Standalone vs Orchestrated modes: Works in standalone VPS debugging or as part of an automated /deploy-otterstack workflow.
  • Use Case: When a deployment stalls at the health_check stage, this skill guides the resolution steps and confirms a healthy rollout.

Quick Start

Use the skill to debug a VPS deployment by running the following against the Archivist VPS:

Frequently Asked Questions about debug-vps-deployment

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

FAQPage Schema
How do I debug a stalled VPS deployment via SSH?

You can debug a stalled VPS deployment by establishing an SSH connection, triggering the deployment script, capturing error logs, and iteratively applying fixes until health checks pass.

What is the best way to automate diagnosing container issues on a VPS?

Automating container issue diagnosis involves running iterative health checks against the deployed services, capturing failure logs, and applying scripted fixes until the orchestrated containers report a healthy status.

Can I use automated debugging for standalone VPS troubleshooting, or does it require an orchestration workflow?

Automated debugging works in both standalone VPS troubleshooting and orchestrated deployment workflows, allowing you to iteratively resolve errors and confirm healthy rollouts in either mode.

Why does my deployment stall at the health check stage, and how can I resolve it?

Deployments stall at the health check stage when services fail to initialize properly; resolution requires triggering the deployment, capturing the specific service errors, and applying fixes until health checks pass.

Do I need SSH access to troubleshoot production VPS deployment errors?

Yes, SSH access to the target VPS is required to trigger deployments, capture error outputs, apply manual or scripted fixes, and verify that services become healthy.