railway-deploy
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.
What this skill does
# 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. ```bash railway up --detach ``` ### CI Mode Streams build logs until complete. Use when user wants to watch the build or needs to debug issues. ```bash 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: ```bash railway up --detach --service backend ``` ## Deploy to Unlinked Project Deploy to a project without linking first: ```bash 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
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.