home / skills / chachamaru127 / claude-code-harness / deploy

deploy skill

/skills/deploy

This skill helps you deploy to Vercel or Netlify and configure analytics and health checks for production, ensuring reliable live environments.

npx playbooks add skill chachamaru127/claude-code-harness --skill deploy

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.5 KB
---
name: deploy
description: "VercelやNetlifyへいざ出陣。本番環境への片道切符を手配します。Use when user mentions deployment, Vercel, Netlify, analytics, or health checks. Do NOT load for: implementation work, local development, reviews, or setup."
description-en: "Deploy to Vercel/Netlify. One-way ticket to production arranged. Use when user mentions deployment, Vercel, Netlify, analytics, or health checks. Do NOT load for: implementation work, local development, reviews, or setup."
description-ja: "VercelやNetlifyへいざ出陣。本番環境への片道切符を手配します。Use when user mentions deployment, Vercel, Netlify, analytics, or health checks. Do NOT load for: implementation work, local development, reviews, or setup."
allowed-tools: ["Read", "Write", "Edit", "Bash"]
disable-model-invocation: true
argument-hint: "[vercel|netlify|health]"
context: fork
---

# Deploy Skills

デプロイとモニタリングの設定を担当するスキル群です。

## 機能詳細

| 機能 | 詳細 |
|------|------|
| **デプロイ設定** | See [references/deployment-setup.md](references/deployment-setup.md) |
| **アナリティクス** | See [references/analytics.md](references/analytics.md) |
| **環境診断** | See [references/health-checking.md](references/health-checking.md) |

## 実行手順

1. ユーザーのリクエストを分類
2. 上記の「機能詳細」から適切な参照ファイルを読む
3. その内容に従って設定

Overview

This skill handles deployments to Vercel and Netlify and configures production monitoring and analytics. It prepares a one-way release to production, verifies environment health, and wires basic analytics. Use it only when the request explicitly concerns deployment, hosting providers, analytics, or runtime health checks.

How this skill works

When triggered by a deployment-related request, the skill classifies the intent and selects the relevant reference procedures for deployment setup, analytics, or health checks. It reads the corresponding guidance and produces concrete deployment steps: environment variables, build settings, domain and DNS instructions, and post-deploy health verifications. It does not perform local development, code implementation, or code reviews—only production-facing deployment and monitoring tasks.

When to use it

  • You need to deploy an app to Vercel or Netlify for production.
  • You want to configure or verify analytics for a production site.
  • You need a production health check or uptime/response verification.
  • You require domain, DNS, or build environment guidance for a production release.
  • You want rollout or rollback recommendations for a production deploy.

Best practices

  • Validate builds and test production-like artifacts before publishing to production.
  • Centralize and securely inject environment variables; avoid committing secrets to source control.
  • Configure basic health checks and uptime monitors immediately after deployment.
  • Enable analytics and error monitoring in production to capture real user metrics and failures.
  • Prepare a rollback or canary strategy for risky releases and document the rollback steps.

Example use cases

  • Create step-by-step production deployment instructions for a Next.js app to Vercel including environment variables and domain setup.
  • Configure site-level analytics and privacy-friendly tracking for a Netlify-hosted site.
  • Run a production environment health checklist that verifies builds, environment vars, status endpoints, and sample user flows.
  • Recommend DNS and HTTPS configuration for a custom domain on Vercel or Netlify and describe TTL considerations.
  • Outline a rollback and monitoring plan to reduce downtime after a problematic release.

FAQ

Can this skill modify source code or perform local development tasks?

No. This skill focuses on production deployment and monitoring procedures. It does not edit source code or run local development workflows.

Will it perform the deployment automatically for me?

No. It produces concrete deployment steps and configuration guidance. Actual deployment execution should be performed by your CI/CD pipeline, hosting console, or authorized automation.