Railway Status
Check the current Railway project status for this directory.
When to Use
- User asks about Railway status, project, services, or deployments
- User mentions deploying or pushing to Railway
- Before any Railway operation (deploy, update service, add variables)
- User asks about environments or domains
When NOT to Use
Use the railway-environment skill instead when user wants:
- Detailed service configuration (builder type, dockerfile path, build command, root directory)
- Deploy config (start command, restart policy, healthchecks, predeploy command)
- Service source (repo, branch, image)
- Compare service configs
- Query or change environment variables
Check Status
Run:
railway status --json
First verify CLI is installed:
command -v railway
Handling Errors
CLI Not Installed
If command -v railway fails:
Railway CLI is not installed. Install with:
npm install -g @railway/cli
or
brew install railway
Then authenticate: railway login
Not Authenticated
If railway whoami fails:
Not logged in to Railway. Run:
railway login
No Project Linked
If status returns "No linked project":
No Railway project linked to this directory.
To link an existing project: railway link
To create a new project: railway init
Presenting Status
Parse the JSON and present:
- Project: name and workspace
- Environment: current environment (production, staging, etc.)
- Services: list with deployment status
- Active Deployments: any in-progress deployments (from
activeDeployments field)
- Domains: any configured domains
Example output format:
Project: my-app (workspace: my-team)
Environment: production
Services:
- web: deployed (https://my-app.up.railway.app)
- api: deploying (build in progress)
- postgres: running
The activeDeployments array on each service shows currently running deployments
with their status (building, deploying, etc.).
1---2name: railway-status3description: Check current Railway project status for this directory. Use when user asks "railway status", "is it running", "what's deployed", "deployment status", or about uptime. NOT for variables or configuration queries - use railway-environment skill for those.4version: 1.0.05author: Railway6license: MIT7tags: [Railway, Status, Project, Environment, Deployment, Infrastructure]8dependencies: [railway-cli]9allowed-tools: Bash(railway:*), Bash(which:*), Bash(command:*)10---1112# Railway Status1314Check the current Railway project status for this directory.1516## When to Use1718- User asks about Railway status, project, services, or deployments19- User mentions deploying or pushing to Railway20- Before any Railway operation (deploy, update service, add variables)21- User asks about environments or domains2223## When NOT to Use2425Use the railway-environment skill instead when user wants:26- Detailed service configuration (builder type, dockerfile path, build command, root directory)27- Deploy config (start command, restart policy, healthchecks, predeploy command)28- Service source (repo, branch, image)29- Compare service configs30- Query or change environment variables3132## Check Status3334Run:35```bash36railway status --json37```3839First verify CLI is installed:40```bash41command -v railway42```4344## Handling Errors4546### CLI Not Installed47If `command -v railway` fails:4849> Railway CLI is not installed. Install with:50> ```51> npm install -g @railway/cli52> ```53> or54> ```55> brew install railway56> ```57> Then authenticate: `railway login`5859### Not Authenticated60If `railway whoami` fails:6162> Not logged in to Railway. Run:63> ```64> railway login65> ```6667### No Project Linked68If status returns "No linked project":6970> No Railway project linked to this directory.71>72> To link an existing project: `railway link`73> To create a new project: `railway init`7475## Presenting Status7677Parse the JSON and present:78- **Project**: name and workspace79- **Environment**: current environment (production, staging, etc.)80- **Services**: list with deployment status81- **Active Deployments**: any in-progress deployments (from `activeDeployments` field)82- **Domains**: any configured domains8384Example output format:85```86Project: my-app (workspace: my-team)87Environment: production8889Services:90- web: deployed (https://my-app.up.railway.app)91- api: deploying (build in progress)92- postgres: running93```9495The `activeDeployments` array on each service shows currently running deployments96with their status (building, deploying, etc.).
metinduraktr-44