Deploy services, inspect logs, and monitor project status on Railway via its CLI.
npx skills add https://github.com/Claudfather/clauDNA --skill railway-claudfather
Please help me install this Agent Skill. Skill: railway Source: https://github.com/Claudfather/clauDNA/tree/main/skills/railway Command: npx skills add https://github.com/Claudfather/clauDNA --skill railway-claudfather
railway up --ci, then verifies health via HTTP checks and post-deploy log review. - Log Investigation: Fetches and filters service logs by level, time range, or pattern to diagnose errors, OOM kills, connection failures, and crash loops. - Status Dashboard: Presents project info, services, recent deployments, environments, variable names, and GraphQL-based resource metrics in one view. - Use Case: After pushing a new commit, ask to deploy your Railway service — the Skill summarizes the change, waits for your confirmation, deploys, health-checks the public domain, and reports any error-level logs. ## Quick Start Ask the assistant to deploy your Railway service, show recent error logs, or display the project status dashboard.High-intent search queries and answers about installing and using this skill.
Use `railway up --ci -m "message"` after confirming the project is linked with `railway status`. This Skill adds pre-deploy git checks, a user confirmation gate, health checks on public domains, and a post-deploy log review.
Run `railway logs --filter "@level:error" --lines 100 --json` to fetch only error entries. The Skill parses the JSON output directly and can also match patterns like OOM, ECONNREFUSED, or crash indicators case-insensitively.
Railway CLI version 4.27.3 or higher is required for the deploy mode. The Skill's pre-flight ladder checks the installed version and prompts an update via `npm update -g @railway/cli` if below the gate.
Yes, `railway down -y` stops the current deployment while keeping the service intact. Because it is destructive, the Skill always asks for explicit confirmation before running it and shows relevant error logs first.
Metrics require an auth token at `.user.token` in `~/.railway/config.json`. If the file or token is missing, the metrics step is skipped with a note, while the rest of the dashboard still renders normally.
onejsAutomate Railway project deployment, management, and observability via the Railway CLI.
asfbay-bitMonitor application health, track errors, and manage incidents post-deployment.
Buckeyes22Deploy backend services, manage environment variables, and provision databases via the Railway CLI.
apeejay-educationDetect hosting platforms and write CLAUDE.md deployment configurations for gstack projects.