How do I install the Deploy skill?

Run npx skillmds@latest add tomevault-io/deploy-29 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Deploy?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Deploy by tomevault-io — Agent Skill

Name: Deploy
Author: tomevault-io

File contents

Deploy Application

Deploy this application to the $ARGUMENTS environment.

Parse the arguments:

First argument: environment (staging or production). Default to staging if not specified.
--skip-build: Skip Docker build/push, deploy with existing image
--dry-run: Render Helm templates and show diff without actually deploying

Pre-flight Checks

Before deploying, verify ALL of these:

Git status is clean - no uncommitted changes (warn if dirty, ask to continue)
On correct branch - develop for staging, main for production
Read package.json to get the current app version
Sync Chart.yaml appVersion with the version from package.json

Helm lint passes with the target values file:

helm lint helm/goravel-blog -f helm/goravel-blog/values.<env>.yaml

Build Phase (skip if --skip-build)

Read DOCKER_REGISTRY and DOCKER_IMAGE_NAME from .env (fallbacks: docker.io and books-database). Construct the full image name: $DOCKER_REGISTRY/<dockerhub-username>/$DOCKER_IMAGE_NAME

Build Docker image:

docker build -t $DOCKER_REGISTRY/<username>/$DOCKER_IMAGE_NAME:<tag> \
  --build-arg BUILD_DATE=$(date -u +'%Y-%m-%dT%H:%M:%SZ') \
  --build-arg VCS_REF=$(git rev-parse --short HEAD) \
  .

For staging: tag = develop
For production: tag = version from package.json

Scan image with Trivy (if available):
```
docker run --rm aquasec/trivy image --severity CRITICAL,HIGH $IMAGE:<tag>
```
Report findings but don't block unless CRITICAL vulnerabilities found.
Push image:
```
docker push $IMAGE:<tag>
```

Deploy Phase

Dry Run Mode (--dry-run)

Render templates and show what would change:

helm template goravel-blog helm/goravel-blog -f helm/goravel-blog/values.<env>.yaml
helm diff upgrade goravel-blog helm/goravel-blog -f helm/goravel-blog/values.<env>.yaml -n <namespace>

Stop here for dry-run.

Actual Deployment

Determine namespace: books-staging or books-production

Run Helm upgrade:

helm upgrade --install goravel-blog helm/goravel-blog \
  -f helm/goravel-blog/values.<env>.yaml \
  -n <namespace> --create-namespace \
  --set image.tag=<tag> \
  --atomic --timeout 10m \
  --wait

For production, ask for explicit confirmation before executing.

Verify rollout:

kubectl rollout status deployment/goravel-blog -n <namespace> --timeout=300s

Post-Deploy Verification

Check pod status:

kubectl get pods -n <namespace> -l app.kubernetes.io/name=goravel-blog

Get ingress URL:
```
kubectl get ingress -n <namespace>
```
Smoke test the health endpoint (if accessible):
```
curl -sf https://<host>/health
```

Rollback

If deployment fails, Helm --atomic auto-rolls back. If post-deploy checks fail, offer to run:

helm rollback goravel-blog -n <namespace>

Summary

Output a deployment summary table:

Item	Value
Environment	staging/production
Version	x.y.z
Image	$DOCKER_REGISTRY//$DOCKER_IMAGE_NAME:tag
Namespace	books-xxx
Status	SUCCESS/FAILED
URL	https://...

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: deploy-29description: Deploy the application to staging or production. Validates, builds, pushes Docker image, deploys via Helm, and runs smoke tests. Use when this capability is needed.---# Deploy ApplicationDeploy this application to the **$ARGUMENTS** environment.Parse the arguments:- First argument: environment (`staging` or `production`). Default to `staging` if not specified.- `--skip-build`: Skip Docker build/push, deploy with existing image- `--dry-run`: Render Helm templates and show diff without actually deploying## Pre-flight ChecksBefore deploying, verify ALL of these:1. **Git status is clean** - no uncommitted changes (warn if dirty, ask to continue)2. **On correct branch** - `develop` for staging, `main` for production3. **Read `package.json`** to get the current app version4. **Sync Chart.yaml appVersion** with the version from package.json5. **Helm lint passes** with the target values file: ```bash helm lint helm/goravel-blog -f helm/goravel-blog/values.<env>.yaml ```## Build Phase (skip if --skip-build)Read `DOCKER_REGISTRY` and `DOCKER_IMAGE_NAME` from `.env` (fallbacks: `docker.io` and `books-database`).Construct the full image name: `$DOCKER_REGISTRY/<dockerhub-username>/$DOCKER_IMAGE_NAME`1. **Build Docker image:** ```bash docker build -t $DOCKER_REGISTRY/<username>/$DOCKER_IMAGE_NAME:<tag> \ --build-arg BUILD_DATE=$(date -u +'%Y-%m-%dT%H:%M:%SZ') \ --build-arg VCS_REF=$(git rev-parse --short HEAD) \ . ``` - For staging: tag = `develop` - For production: tag = version from package.json2. **Scan image with Trivy** (if available): ```bash docker run --rm aquasec/trivy image --severity CRITICAL,HIGH $IMAGE:<tag> ``` Report findings but don't block unless CRITICAL vulnerabilities found.3. **Push image:** ```bash docker push $IMAGE:<tag> ```## Deploy Phase### Dry Run Mode (--dry-run)Render templates and show what would change:```bashhelm template goravel-blog helm/goravel-blog -f helm/goravel-blog/values.<env>.yamlhelm diff upgrade goravel-blog helm/goravel-blog -f helm/goravel-blog/values.<env>.yaml -n <namespace>```Stop here for dry-run.### Actual Deployment1. **Determine namespace**: `books-staging` or `books-production`2. **Run Helm upgrade:** ```bash helm upgrade --install goravel-blog helm/goravel-blog \ -f helm/goravel-blog/values.<env>.yaml \ -n <namespace> --create-namespace \ --set image.tag=<tag> \ --atomic --timeout 10m \ --wait ``` For production, ask for explicit confirmation before executing.3. **Verify rollout:** ```bash kubectl rollout status deployment/goravel-blog -n <namespace> --timeout=300s ```## Post-Deploy Verification1. **Check pod status:** ```bash kubectl get pods -n <namespace> -l app.kubernetes.io/name=goravel-blog ```2. **Get ingress URL:** ```bash kubectl get ingress -n <namespace> ```3. **Smoke test** the health endpoint (if accessible): ```bash curl -sf https://<host>/health ```## RollbackIf deployment fails, Helm `--atomic` auto-rolls back. If post-deploy checks fail, offer to run:```bashhelm rollback goravel-blog -n <namespace>```## SummaryOutput a deployment summary table:| Item | Value ||------|-------|| Environment | staging/production || Version | x.y.z || Image | $DOCKER_REGISTRY/<username>/$DOCKER_IMAGE_NAME:tag || Namespace | books-xxx || Status | SUCCESS/FAILED || URL | https://... |---> Converted and distributed by [TomeVault](https://tomevault.io/claim/liwoo) — claim your Tome and manage your conversions.

Frequently asked questions

Deploy