railway-deploy
Deploys code to Railway using the CLI with support for background processes and build monitoring.
Install
mkdir -p .claude/skills/railway-deploy && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4494" && unzip -o skill.zip -d .claude/skills/railway-deploy && rm skill.zipInstalls to .claude/skills/railway-deploy
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Deploy code to Railway using "railway up". Use when user wants to push code, says "railway up", "deploy", "ship", or "push". For initial setup or creating services, use railway-new skill. For Docker images, use railway-environment skill.Key capabilities
- →Execute remote deployments using railway up
- →Tail real-time build logs via CI mode
- →Target specific project environments
- →Deploy services from subdirectories
- →Stream build status to terminal
How it works
Triggers the Railway CLI to upload the current directory context and initiate a remote build pipeline.
Inputs & outputs
When to use railway-deploy
- →Deploy local application updates
- →Stream build logs during deployment
- →Push code to production or staging
- →Debug build failures
About this skill
Railway Deploy
Deploy code from the current directory to Railway using railway up.
When to Use
- User asks to "deploy", "ship", "push code"
- User says "railway up" or "deploy to Railway"
- User wants to deploy local code changes
- User says "deploy and fix any issues" (use --ci mode)
Modes
Detach Mode (default)
Starts deploy and returns immediately. Use for most deploys.
railway up --detach
CI Mode
Streams build logs until complete. Use when user wants to watch the build or needs to debug issues.
railway up --ci
When to use CI mode:
- User says "deploy and watch", "deploy and fix issues"
- User is debugging build failures
- User wants to see build output
Deploy Specific Service
Default is linked service. To deploy to a different service:
railway up --detach --service backend
Deploy to Unlinked Project
Deploy to a project without linking first:
railway up --project <project-id> --environment production --detach
Requires both --project and --environment flags.
CLI Options
| Flag | Description |
|---|---|
-d, --detach | Don't attach to logs (default) |
-c, --ci | Stream build logs, exit when done |
-s, --service <NAME> | Target service (defaults to linked) |
-e, --environment <NAME> | Target environment (defaults to linked) |
-p, --project <ID> | Target project (requires --environment) |
[PATH] | Path to deploy (defaults to current directory) |
Directory Linking
Railway CLI walks UP the directory tree to find a linked project. If you're in a subdirectory of a linked project, you don't need to relink.
For subdirectory deployments, prefer setting rootDirectory via the railway-environment skill, then deploy normally with railway up.
After Deploy
Detach mode
Deploying to <service>...
Use railway-deployment skill to check build status (with --lines flag).
CI mode
Build logs stream inline. If build fails, the error will be in the output.
Do NOT run railway logs --build after CI mode - the logs already streamed. If you need
more context, use railway-deployment skill with --lines flag (never stream).
Composability
- Check status after deploy: Use railway-service skill
- View logs: Use railway-deployment skill
- Fix config issues: Use railway-environment skill
- Redeploy after config fix: Use railway-environment skill
Error Handling
No Project Linked
No Railway project linked. Run `railway link` first.
No Service Linked
No service linked. Use --service flag or run `railway service` to select one.
Build Failure (CI mode)
The build logs already streamed - analyze them directly from the railway up --ci output.
Do NOT run railway logs after CI mode (it streams forever without --lines).
Common issues:
- Missing dependencies → check package.json/requirements.txt
- Build command wrong → use railway-environment skill to fix
- Dockerfile issues → check dockerfile path
When not to use it
- →When the local project is not initialized with Railway
- →For massive Docker images requiring separate storage
Prerequisites
Limitations
- →Depends on Railway CLI availability
- →Requires active project link
How it compares
It wraps complex CLI flags into a single command that manages remote state and build synchronization.
Compared to similar skills
railway-deploy side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| railway-deploy (this skill) | 1 | 7mo | Review | Beginner |
| deployment-pipeline-design | 6 | 2mo | Review | Advanced |
| cloudflare-deploy | 3 | 6mo | Review | Intermediate |
| deployment-engineer | 4 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by davila7
View all by davila7 →You might also like
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
cloudflare-deploy
davila7
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
deployment-engineer
sickn33
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.
managing-deployment-rollbacks
jeremylongshore
Deploy use when you need to work with deployment and CI/CD. This skill provides deployment automation and orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
DevOps / CI-CD Engineer
dr-pabs
Automate build, validation, deployment, and release operations for the project.
deployment-patterns
DekaPrayoga
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.