Back to Skills
Skill

deploy

Unified deployment for multiple platforms. Supports Railway, Cloudflare Pages, and Cloudflare Workers. Use when user says "/deploy", "배포", "deploy all", "railway 배포", "cloudflare 배포", or any deployment-related request. Supports selective deployment targets.

From deploy
Install
1
Run in your terminal
$
npx claudepluginhub october-academy/agent-plugins --plugin deploy
Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Deploy Skill

Unified deployment automation for multi-service projects.

Supported Platforms

PlatformCommandUse Case
Railwayrailway upBackend services, bots
Cloudflare PagesGit push (auto-deploy)Static sites
Cloudflare Pages (OpenNext)bunx @opennextjs/cloudflare build && bunx wrangler deployNext.js SSR apps
Cloudflare Workerswrangler deployEdge functions

Usage

Commands

/deploy              # Deploy all services
/deploy railway      # Railway only
/deploy cf           # Cloudflare Workers only
/deploy web          # Next.js app via OpenNext
/deploy opennext     # Same as /deploy web
/deploy pages        # Static sites (git push auto-deploy)

Korean Triggers

  • "배포해줘" - full deployment
  • "railway 배포" - Railway only
  • "cloudflare 배포" - Cloudflare only

Workflow

1. Pre-deployment Check

Before deploying, verify:

git status                    # Check for uncommitted changes
git log -1 --oneline          # Verify current commit

If uncommitted changes exist, ask user whether to:

  • Commit first
  • Deploy anyway (warn about uncommitted changes)

2. Deploy Railway

cd <project-root>/<service-dir> && railway up

Common service directories: discord-bot/, backend/, api/

3. Deploy Cloudflare Workers

cd <project-root>/apps/workers && bunx wrangler deploy
# OR
cd <project-root>/workers && npx wrangler deploy

4. Cloudflare Pages (Static)

Pages auto-deploys on git push to main branch. Remind user:

git push origin main

Check deployment status at: https://dash.cloudflare.com

5. Cloudflare Pages (OpenNext for Next.js)

For Next.js apps with SSR/API routes, use OpenNext:

cd <project-root>/apps/web && bunx @opennextjs/cloudflare build && bunx wrangler deploy

This builds the Next.js app for Cloudflare Workers runtime and deploys it.

Post-deployment

After successful deployment:

  1. Report status for each service
  2. Provide relevant URLs/dashboards
  3. Note any warnings or errors

Configuration

Projects should have these in their root or service directories:

  • railway.toml - Railway configuration
  • wrangler.toml - Cloudflare Workers configuration

Error Handling

ErrorSolution
"Not logged in"Run railway login or wrangler login
"Project not found"Run railway link or check wrangler.toml
"Build failed"Check build logs, fix issues, retry
Similar Skills
cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.5k
Stats
Parent Repo Stars0
Parent Repo Forks1
Last CommitFeb 3, 2026
Actions
View SourceView PluginView on GitHubView README