vps-debugging

Diagnose Strut VPS deployments with health checks, container status, and log reviews.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/gfargo/strut --skill vps-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vps-debugging
Source: https://github.com/gfargo/strut/tree/main/.kiro/skills/vps-debugging
Command: npx skills add https://github.com/gfargo/strut --skill vps-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Troubleshooting and debugging procedures for Strut VPS deployments. Use to diagnose production issues, check container status, view logs, or debug deployment problems.

Core Features & Use Cases

  • Quick diagnostics for health, status, and logs.
  • Guided commands for common VPS deployment problems (e.g., 502 Bad Gateway, port conflicts, startup failures).
  • Real-world scenarios across multiple stacks to stabilize services quickly.

Quick Start

Run a quick health check and status review for your stack in prod.

Frequently Asked Questions about vps-debugging

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

FAQPage Schema
How do I diagnose VPS deployment issues like 502 Bad Gateway or startup failures?

To diagnose VPS deployment issues, run quick health checks and container status reviews to identify root causes of 502 Bad Gateway or startup failures. It applies CLI workflows to verify and recover services across multiple stacks.

What is the best way to check container health and status in a production environment?

Checking container health and status involves running diagnostic CLI workflows that review service logs and deployment states. This validates container health and verifies service stability across your production stack.

Can I use standard CLI commands to view logs and troubleshoot Strut VPS deployments?

Yes, you can use CLI commands like health, status, logs, and exec to troubleshoot Strut VPS deployments. These commands allow you to review container logs and debug deployment problems directly in production.

Why does my VPS deployment fail to start, and how can I fix it?

Your VPS deployment may fail to start due to port conflicts or container issues, which you can fix by running diagnostic health checks and reviewing deployment logs. Guided remediation commands help verify and recover services.

Does this approach work for diagnosing issues across multiple stacks?

Yes, this diagnostic approach works across multiple stacks to stabilize services quickly in production environments. It implements CLI workflows to verify and recover services regardless of the underlying stack.