Debug Ops

Diagnose production issues using Railway logs by collecting and filtering traces to surface frontend, backend, or API failures, then mapping request paths to identify the failing service. The skill provides a structured workflow from log collection through root-cause analysis and verification.

Tracing intermittent 500 errors involves mapping end-to-end request paths from the UI to databases and external APIs. The skill systematically identifies error types, failing services, and data issues by pattern matching against collected Railway logs to locate the bottleneck.

Finding the root cause of an API bottleneck requires end-to-end tracing across your production environment. The skill analyzes Railway logs to pinpoint failing services, maps request paths to external APIs, and provides structured steps to validate and verify the fix.

Log analysis can fix frontend and backend failures simultaneously by collecting and filtering Railway logs to surface errors across all services. The skill routes issues to frontend-expert or api-developer handoff cues when code changes are needed.

Structured troubleshooting works for system bottlenecks in production by applying a guided remediation workflow. It collects Railway logs, performs pattern matching, conducts root-cause diagnosis, and provides verification steps to ensure the bottleneck is resolved.

Use end-to-end tracing instead of standard log collection when you need to map request paths from UI to databases and external APIs to locate bottlenecks. It is essential for diagnosing complex production issues where the failing service is not immediately obvious from isolated logs.