Skill

app-deployment

Deploy applications via git-push-to-deploy workflow - set up production remotes, push code, manage environment variables, restart containers. Triggers on phrases like "deploy an app", "deploy this app", "push code to server", "set up deployment", "git push deploy", "restart app", "copy env to server", "set up production remote".

npx claudepluginhub the-focus-ai/claude-marketplace --plugin marina-skill

Tool Access

This skill is limited to using the following tools:

BashRead

Preview

You help deploy applications using a git-push-to-deploy workflow.

Supporting Assets

references/deployment-reference.md

SKILL.md

Similar Skills

ui-ux-pro-max

70.8k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

context7-mcp

51.8k

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

competitive-landscape

32.9k

Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.

startup-business-analyst

Stats

Stars2

Forks0

Last CommitFeb 11, 2026

Actions

View Source View Plugin View on GitHub View README

App Deployment Skill

You help deploy applications using a git-push-to-deploy workflow.

Setup

Run bash ${CLAUDE_PLUGIN_ROOT}/scripts/check-deps.sh to verify tools are available.

How Deployment Works

User runs git push production main
SSH connects to server as deploy user
SSH forced-command routes to deployer script
deployer creates a bare git repo (first time), receives the push
post-receive hook checks out code and runs docker build
deployer stops old container and starts new one with Caddy labels
Caddy automatically provisions HTTPS and reverse proxies to port 8080

App requirements:

Must have a Dockerfile in the project root
Container must listen on port 8080

Scripts

Deployment utilities use ${CLAUDE_PLUGIN_ROOT}/scripts/deploy.sh:

Copy env to server

bash ${CLAUDE_PLUGIN_ROOT}/scripts/deploy.sh env

Copies .env.production (preferred) or .env to the server and restarts the container.

Restart container

bash ${CLAUDE_PLUGIN_ROOT}/scripts/deploy.sh restart

Force rebuild

bash ${CLAUDE_PLUGIN_ROOT}/scripts/deploy.sh push-empty

Creates an empty commit and pushes to trigger a full rebuild.

Show remote info

bash ${CLAUDE_PLUGIN_ROOT}/scripts/deploy.sh info

Setting Up a New Deployment

Walk the user through these steps:

Check prerequisites:
- Verify Dockerfile exists
- Check the app listens on port 8080
Check for existing remote: git remote -v | grep production
If no production remote, guide setup: a. List servers: bash ${CLAUDE_PLUGIN_ROOT}/scripts/server.sh list b. Discover domains: bash ${CLAUDE_PLUGIN_ROOT}/scripts/dns.sh list-zones c. Pick/create server and choose app name d. Add remote: git remote add production deploy@<server>.<domain>:<appname>.<domain> e. Add DNS: bash ${CLAUDE_PLUGIN_ROOT}/scripts/dns.sh add <appname>.<domain> <server_ip> f. Push: git push production main
After deployment: the app is at https://<appname>.<domain> (Caddy handles HTTPS).

Git Remote Format

deploy@<server-hostname>:<site-fqdn>

Example: deploy@web1.example.com:myapp.example.com

The site FQDN becomes both the Docker container name and the hostname Caddy uses for routing/HTTPS.

Behavior

Check for Dockerfile before attempting deployment
When setting up, show the full git remote URL and confirm
After deployment, tell the user the app URL
If deployment fails, suggest checking logs: ssh deploy@<server> (shows last 20 log entries)
Warn about sensitive values before copying env files