setup-deploy

Detect and persist deployment configurations to CLAUDE.md for the /land-and-deploy workflow.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/rkumar261/studio-cast --skill setup-deploy-rkumar261
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/rkumar261/studio-cast/tree/main/.claude/skills/gstack/setup-deploy
Command: npx skills add https://github.com/rkumar261/studio-cast --skill setup-deploy-rkumar261

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic.

Core Features & Use Cases

  • Auto-detects deployment platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, or custom) and infers production URL.
  • Guides the user through platform-specific steps to configure deploy status commands and health checks.
  • Writes and maintains an idempotent CLAUDE.md Deploy Configuration section so future deployments are automatically aligned.

Quick Start

Run /setup-deploy to detect your deployment configuration and persist it to CLAUDE.md.

Frequently Asked Questions about setup-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure deployment settings for multiple hosting platforms like Fly.io and Vercel?

Deployment configuration for platforms like Fly.io, Render, Vercel, Netlify, Heroku, and GitHub Actions is auto-detected and persisted to CLAUDE.md. This ensures future deployments remain automatically aligned without manual reconfiguration.

What is the best way to automate deploy status commands and health check endpoint detection?

Automating deploy status commands and health checks involves detecting your hosting platform and guiding you through platform-specific configuration steps. The resulting settings are written idempotently to CLAUDE.md as a single source of truth.

Can I use CLAUDE.md as a single source of truth for deployment configuration and production URL inference?

CLAUDE.md serves as the single source of truth for deployment configuration, storing platform detection results, inferred production URLs, health check endpoints, and deploy status commands for automated future workflows.

How do I set up idempotent deployment configuration writes to avoid duplicate entries?

Idempotent writes to CLAUDE.md ensure deployment configuration sections are safely updated without creating duplicate entries. The process validates existing content and performs guarded edits to maintain configuration integrity.

Does the deployment configuration workflow support custom hosting platforms outside of standard providers?

Custom hosting platforms are supported alongside standard providers like Fly.io, Render, Vercel, Netlify, Heroku, and GitHub Actions. The detection process applies platform-specific logic and guided prompts to configure any deployment target.

Why do I need to run deployment configuration detection before using the land-and-deploy workflow?

Running deployment configuration detection before land-and-deploy workflows ensures your hosting platform, production URL, health checks, and deploy commands are identified and persisted. This enables fully automatic future deployments without manual intervention.