render-debug
Audited by Runlayer on Feb 23, 2026
Malicious tool definition detected
Tool: SKILL.md [1/2] Description: --- name: render-debug description: Debug failed Render deployments by analyzing logs, metrics, and database state.
Tool: SKILL.md [2/2]
Malicious tool definition detected
Tool: references/database-debugging.md [1/2] Description: # Database Debugging Diagnose and fix PostgreSQL database issues on Render using MCP tools.
Tool: references/database-debugging.md [2/2]
Malicious tool definition detected
Tool: references/error-patterns.md [1/3] Description: # Render Deployment Error Patterns Comprehensive catalog of common deployment errors on Render, their causes, and fixes.
Tool: references/error-patterns.md [2/3] Description: Pool({ connectionString: process.env.DATABASE_URL, ssl: process.env.NODE_ENV === 'production' ? { rejectUnauthorized: false } : false }); ``` **Step 3:** Check database provisioned ```bash render services -o json # Verify database exists and is active ``` --- ### 5. INVALID_BUILD_COMMAND **Description:** Build command fails.
Tool: references/error-patterns.md [3/3] Description: Match:** - `EACCES: permission denied` - `Error: EPERM: operation not permitted` - `PermissionError: [Errno 13] Permission denied` **Root Causes:** 1.
Malicious tool definition detected
Tool: references/log-analysis.md [1/2] Description: # Render Log Analysis Guide How to read, interpret, and analyze Render logs to identify deployment and runtime issues. ## Understanding Render Logs ### Log Types Render provides different log types for different purposes: 1.
Tool: references/log-analysis.md [2/2] Description: ```bash render logs -r <service-id> -o json | grep "DATABASE_URL" ``` ### 3.
Malicious tool definition detected
Tool: references/metrics-debugging.md Description: # Metrics-Based Debugging Use Render metrics to diagnose performance issues, resource constraints, and application health problems.
Malicious tool definition detected
Tool: references/quick-workflows.md Description: # Quick Debugging Workflows Step-by-step MCP tool sequences for common debugging scenarios. ## Deploy Failures ### "Why did my deploy fail?" ``` # 1.
Malicious tool definition detected
Tool: references/troubleshooting.md [1/2] Description: # Render Troubleshooting Guide Systematic debugging procedures and fix strategies for common Render deployment issues. ## General Debugging Process ### The 5-Step Debugging Method 1.
Tool: references/troubleshooting.md [2/2] Description: Configure in render.yaml ```yaml healthCheckPath: /health ``` **Step 3:** Optimize startup time Move slow operations after server start: ```javascript // Start server first const server = app.listen(PORT, '0.0.0.0', () => { console.log(`Server running on port ${PORT}`); // Then do slow operations initializeCache(); warmupConnections(); }); ``` --- ## Issue Category 6: Memory Issues ### Problem: Out of Memory **Symptoms:** - `JavaScript heap