Status Kit

A Railway skill for checking project and service status — displaying linked project details, service deployments, environment information, and connection details at a glance. Status Kit is the go-to tool for quick situational awareness of your Railway setup.

When to Use This Skill

Choose Status Kit when:

• Checking which Railway project your CLI is linked to
• Viewing the status of all services in a project
• Verifying deployment state before making changes
• Confirming environment and variable configuration

Consider alternatives when:

• You need to modify service configuration (use service management tools)
• You want to view or stream logs (use log viewing tools)
• You need detailed deployment history (use the Railway dashboard)

Quick Start

Copy
claude "Show me the status of my Railway project"

Copy
# View full project status
railway status

# Example output:
# Project: my-app (project-id-xxx)
# Environment: production
# Services:
#   api (Active) - api-xxx.up.railway.app
#   worker (Active) - no domain
#   Postgres (Healthy)
#   Redis (Healthy)

Core Concepts

Status Output Interpretation

Field	Meaning	Values
Project	Currently linked project name	Name + ID
Environment	Active environment scope	dev, staging, production
Service Status	Deployment state	Active, Building, Failed, Removed
Plugin Status	Database health	Healthy, Unhealthy, Starting
Domain	Public URL (if assigned)	*.up.railway.app or custom

Quick Health Check Script

Copy
#!/bin/bash
# railway-health.sh — Quick project health overview

echo "=== Railway Status ==="
railway status

echo ""
echo "=== Recent Logs ==="
railway logs --tail 2>/dev/null | tail -20

echo ""
echo "=== Variables ==="
railway variables 2>/dev/null | grep -v "PASSWORD\|SECRET\|KEY"

Status Workflow

Copy
## Pre-Deployment Checklist

1. `railway status` — Verify correct project/environment
2. `railway variables` — Confirm required vars are set
3. `railway logs` — Check current service is healthy
4. `railway up` — Deploy
5. `railway status` — Verify new deployment is Active
6. `railway logs --tail` — Monitor for startup errors

Configuration

Parameter	Description	Default
show_variables	Include variable names in status	false
show_domains	Include domain assignments	true
show_resources	Include CPU/memory usage	false
environment_filter	Show status for specific environment	Current
output_format	Text, JSON, or table format	text

Best Practices

1. Check status before every deployment. Make railway status a habit before running railway up. It takes 2 seconds and prevents deploying to the wrong project or environment — a mistake that can take much longer to fix.

2. Script status checks into your workflow. Create a shell alias or script that runs railway status and shows the most relevant information. Muscle memory builds faster when the command is short and always available.

3. Use status to verify post-deployment. After deploying, run railway status again to confirm the deployment transitioned from "Building" to "Active." If it stays in "Building" for too long, check logs for build errors.

4. Compare status across environments. Run railway status in both staging and production to verify they're running the same services. Missing services or failed deployments in one environment indicate configuration drift.

5. Include status checks in documentation. When writing deployment runbooks, add railway status checkpoints at key steps. This gives the person following the runbook clear verification points.

Common Issues

Status shows "Not linked to a project." Run railway link to connect your directory to a Railway project. If you recently cloned the repo, the .railway directory wasn't included (it's in .gitignore). Re-link with railway link.

Service shows "Active" but is actually crashed. Without a health check, Railway marks a service as Active once the process starts — even if it crashes immediately and keeps restarting. Add healthcheckPath to your railway.json so Railway accurately reports unhealthy services.

Status shows old deployment information. The CLI caches some data. Run railway status with a fresh terminal session if the displayed information seems stale. For real-time data, check the Railway dashboard or use railway logs --tail.