Perfect for Development Agents needing streamlined code deployment to Railway. This skill should be used when the user wants to push code to Railway, says railway up, deploy, deploy to railway, ship, or push. For initial setup or creating services, use new skill. For Docker imag

How do I install deploy?

Run the command: npx killer-skills add matixlol/monitoreo-panama/deploy. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for deploy?

Key use cases include: Deploying updated application code, Shipping new features to Railway, Pushing local code fixes.

Which IDEs are compatible with deploy?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for deploy?

Requires Railway setup. Limited to deploying from the current directory. Needs `railway up` command-line tool installed.

deploy

Install deploy, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md

Readonly

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Supporting Evidence

Deploy

Name: deploy
Availability: InStock
Author: matixlol

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)

Commit Message

Always use the -m flag with a descriptive commit message summarizing what's being deployed:

bash
1railway up --detach -m "Add user authentication endpoint"

Good commit messages:

Describe what changed: "Fix memory leak in worker process"
Reference tickets/issues: "Implement feature #123"
Be concise but meaningful: "Update deps and fix build warnings"

Modes

Detach Mode (default)

Starts deploy and returns immediately. Use for most deploys.

bash
1railway up --detach -m "Deploy description here"

CI Mode

Streams build logs until complete. Use when user wants to watch the build or needs to debug issues.

bash
1railway up --ci -m "Deploy description here"

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:

bash
1railway up --detach --service backend -m "Deploy description here"

Deploy to Unlinked Project

Deploy to a project without linking first:

bash
1railway up --project <project-id> --environment production --detach -m "Deploy description here"

Requires both --project and --environment flags.

CLI Options

Flag	Description
`-m, --message <MSG>`	Commit message describing the deploy (always use this)
`-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 environment skill, then deploy normally with railway up.

After Deploy

Detach mode

Deploying to <service>...

Use 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 deployment skill with --lines flag (never stream).

Composability

Check status after deploy: Use service skill
View logs: Use deployment skill
Fix config issues: Use environment skill
Redeploy after config fix: Use 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 environment skill to fix
Dockerfile issues → check dockerfile path

deploy — community deploy, monitoreo-panama, community, ide skills

About this Skill

Killer-Skills Review

Core Value

Ideal Agent Persona

↓ Capabilities Granted for deploy

! Prerequisites & Limits

Source Boundary

Decide The Next Action Before You Keep Reading Repository Material

Start With Installation And Validation

Cross-Check Against Trusted Picks

Move To Workflow Collections For Team Rollout

Browser Sandbox Environment

⚡️ Ready to unleash?

FAQ & Installation Steps

? Frequently Asked Questions

What is deploy?