railway-debug

Analyze Railway production logs and debug deploy and runtime errors.

1|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill railway-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: railway-debug
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/railway-debug
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill railway-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rapidly identifies and resolves deploy and runtime failures for services running on Railway by guiding log collection, root cause analysis, migration recovery, safe fixes, and post-deploy verification so teams can restore production health faster.

Core Features & Use Cases

  • Log analysis: Collect and filter Railway runtime and build logs to surface errors and stack traces.
  • Migration auditing & recovery: Audit Drizzle migrations, compare local journals with production, and provide idempotent registration or apply recommendations.
  • Safe production DB access: Use Railway public DATABASE_PUBLIC_URL patterns and TLS-aware clients to query production without relying on internal hostnames.
  • Repair workflow: Classify errors (build, runtime, import, DB, auth, memory), propose targeted fixes, validate locally, redeploy, and verify clean logs.
  • Operational guardrails: Detect mega-migrations, recommend NOT applying large migrations blindly, and provide SQL templates for safe registration.

Quick Start

Analyze the production logs for the specified Railway service, identify the root cause, recommend a migration or code fix with safe SQL registration if needed, and outline verification steps before redeploy.

Frequently Asked Questions about railway-debug

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

FAQPage Schema
How do I debug Railway deployment errors using runtime logs?

Debug Railway deployment errors by collecting and filtering build and runtime logs to surface stack traces, classifying the root cause, and applying targeted fixes before redeploying.

What is the best way to fix failed Drizzle migrations on Railway?

Fix failed Drizzle migrations by auditing local journals against production, then applying idempotent migration registration or recommended SQL templates to safely synchronize the database state.

How do I safely connect to a Railway production database for migration checks?

Safely connect to a Railway production database using the public DATABASE_PUBLIC_URL with TLS-aware clients, allowing secure queries and migration registrations without relying on internal hostnames.

Why does my Railway service crash after a successful deployment?

Railway services can crash post-deploy due to runtime, import, database, or memory errors; analyze runtime logs to classify the failure type, validate fixes locally, and verify clean logs after redeploying.

Do I need the Railway CLI to troubleshoot application errors?

Yes, troubleshooting requires Railway CLI access and permissions to view service variables and logs to effectively collect status data and diagnose production failures.

What should I do when facing a mega-migration on Railway?

When facing a mega-migration on Railway, avoid applying it blindly; instead, use operational guardrails to detect large migrations and apply safe SQL templates for controlled registration.