deploy_skill

This skill deploys local code to Railway using railway up, providing quick, detached or CI-mode deployments with logs as needed.

Shell
Official

79

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill railwayapp/railway-skills --skill deploy

SKILL.md3.2 KB

Overview

This skill deploys code from the current working directory to Railway using the Railway CLI. It runs the recommended railway up command in either detached mode (default) or CI mode for streamed logs. Use this skill for pushing local changes, targeting specific services or environments, and deploying to unlinked projects when you provide project and environment flags.

How this skill works

The skill constructs and runs railway up with flags based on user intent: --detach for background deploys or --ci to stream build logs until completion. It can target a linked service, a named service via --service, or an explicit project and environment via --project and --environment. For subdirectory projects, the CLI walks up the tree to find linked metadata; for nonstandard roots, set rootDirectory via the environment skill first.

When to use it

User says “deploy”, “ship”, “push”, or “railway up”
Push local code changes to Railway from the current directory
Watch the build logs live or debug failures (use CI mode)
Deploy to a different service or environment than the linked defaults
Deploy to an unlinked project when you supply project and environment

Best practices

Default to detach mode for routine deploys: railway up --detach
Use CI mode (railway up --ci) when you need to watch build output or troubleshoot
Specify --service to target a nonlinked service or --project and --environment for unlinked projects
Set rootDirectory via the environment skill for subdirectory deployments instead of relinking
After detached deploys, check status with the deployment or service skills rather than re-running logs

Example use cases

Quick background deploy of current code: railway up --detach
Stream build output to debug a failing build: railway up --ci
Deploy a backend service explicitly: railway up --detach --service backend
Push to an unlinked production environment: railway up --project <project-id> --environment production --detach
After fixing config with environment skill, redeploy to verify changes

FAQ

Use --ci when you want to stream build logs and watch or debug the build. Use --detach for faster, nonblocking deploys.

Can I deploy from a subdirectory?

Yes. The CLI walks up the directory tree to find a linked project. For custom roots, set rootDirectory via the environment skill before deploying.