What problem does it solve? Deployments on Render fail for many reasons—missing environment variables, port binding errors, out-of-memory crashes, database connection failures—and finding the root cause requires digging through build logs, runtime logs, metrics, and database state. This Skill provides a structured debugging workflow that identifies the error pattern and applies the correct fix. ## Core Features & Use Cases - Log-Based Error Detection: Query build, runtime, and error logs via Render MCP tools or CLI, then match output against a catalog of 15 known error patterns (missing env vars, EADDRINUSE, OOM, health check timeouts, and more). - Metrics and Database Diagnosis: Inspect CPU, memory, HTTP latency, and connection counts, plus run direct PostgreSQL queries to find slow queries, lock contention, and connection pool exhaustion. - Guided Fix and Verification: Apply fixes such as updating environment variables, then verify with deploy status, fresh error logs, and request metrics. - Use Case: Your web service keeps crashing after deploy. The skill pulls error logs, detects a KeyError: 'DATABASE_URL', adds the variable via update_environment_variables, and confirms the next deploy goes live. ## Quick Start Ask the AI to debug why your Render service failed to deploy and have it check the logs, metrics, and database connections for the root cause.
