deployerphp-debugger

Diagnose DeployerPHP production issues with read-only server commands.

4|Updated Sep 20, 2025

Search Tags:#production #diagnostics #debugger #inventory #read-only #deployerphp-debugger

Ready to run

npx skills add https://github.com/loadinglucian/deployer-php --skill deployerphp-debugger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deployerphp-debugger
Source: https://github.com/loadinglucian/deployer-php/tree/main/scaffolds/ai/deployerphp-debugger
Command: npx skills add https://github.com/loadinglucian/deployer-php --skill deployerphp-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose production issues on DeployerPHP deployments without mutating infrastructure.

Core Features & Use Cases

Read inventory, logs, and service status to triage problems without changes.
Read filesystem and runtime state to surface root causes while preserving server state.
Use Case: An on-call engineer needs to understand why a site is failing without touching the server, then plan a safe remediation.

Quick Start

Run a safe, read-only diagnostic on the target DeployerPHP deployment using server:info and server:logs, then report inventory, service status, and filesystem state.

Frequently Asked Questions about deployerphp-debugger

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

FAQPage Schema

How do I diagnose production issues on a DeployerPHP deployment without modifying the server?▼

To diagnose production issues on a DeployerPHP deployment without modifying the server, use safe, read-only commands like server:info, server:logs, and server:run with explicit environment controls to audit inventory, service status, and filesystem state.

Can I check service status and logs on a live DeployerPHP server without risking infrastructure changes?▼

Yes, you can check service status and logs on a live DeployerPHP server without risking infrastructure changes. The debugger enforces non-destructive read-only operations using server:info and server:logs commands.

What is the safest way to review filesystem and runtime state during a production outage?▼

The safest way to review filesystem and runtime state during a production outage is to use non-interactive, read-only diagnostic commands. This surfaces root causes while preserving server state and preventing accidental mutations.

Does this read-only production debugger work with non-interactive commands?▼

Yes, this read-only production debugger works with non-interactive commands. It enforces safe, non-destructive operations by using server:run with explicit environment controls, ensuring no interactive prompts mutate the infrastructure.

What should I do if I need to triage a failing DeployerPHP site without touching the server?▼

To triage a failing DeployerPHP site without touching the server, run safe read-only diagnostics to read inventory, logs, and service status. This allows you to understand the failure and plan a safe remediation.