Skip to main content

railway-status

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.

Ir a la instalación

Datos de origen

Repositorio
tomevault-io/claude-code-plugins
Última actividad en el origen
6 de abril de 2026 a las 09:15
Idioma detectado de SKILL.md
inglés
Estrellas
3
Forks
2

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
railway-status
description
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.
version
1.0.0
author
Railway
license
MIT
tags
["Railway","Status","Project","Environment","Deployment","Infrastructure"]
dependencies
["railway-cli"]
allowed-tools
Bash(railway:*), Bash(which:*), Bash(command:*)
# 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: ```bash railway status --json ``` First verify CLI is installed: ```bash 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.). --- > Converted and distributed by [TomeVault](https://tomevault.io) | [Claim this content](https://tomevault.io/claim/davila7/claude-code-templates) <!-- tomevault:2.0:skill_md:2026-04-05 -->
Ver en GitHub