setup-deploy

Detect hosting platforms and write deployment configuration to CLAUDE.md.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/curielmc/beat-SPY --skill setup-deploy-curielmc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack/setup-deploy
Command: npx skills add https://github.com/curielmc/beat-SPY --skill setup-deploy-curielmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configures deployment settings for /land-and-deploy across multiple hosting platforms, detects the production URL, health checks, and deploy status commands, and writes the configuration to CLAUDE.md so future deployments run automatically.

Core Features & Use Cases

  • Platform detection for Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom environments.
  • Discovery of production URLs and health check endpoints.
  • Generation and persistence of a Deploy Configuration in CLAUDE.md to enable automated deployments on future runs.
  • Idempotent reconfiguration: re-runs cleanly to update settings when your project changes.

Quick Start

Run the /setup-deploy command to generate and persist your deployment configuration in 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 automate deployment configuration across multiple hosting platforms like Vercel and Render?

Automated deployment configuration detects your hosting platform by inspecting config files, prompts for missing values like production URLs, and persists the settings to CLAUDE.md for future automated runs.

Does platform detection work with Fly.io, Netlify, Heroku, and GitHub Actions?

Platform detection works with Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom environments by inspecting common config files to identify your deployment target automatically.

How do I persist health check endpoints and deploy commands for automated deployments?

You can persist health check endpoints and deploy commands by running an idempotent setup flow that validates URLs and writes a Deploy Configuration section directly to CLAUDE.md.

What's the best way to keep CLAUDE.md in sync when deployment settings change?

Re-running the idempotent setup flow refreshes deployment settings cleanly in CLAUDE.md whenever your project changes, ensuring future deployments run automatically without manual reconfiguration.

Can I re-run deployment setup safely if my production URL or platform changes?

Yes, the configuration flow is idempotent and can re-run safely to update settings, detecting new platform configurations and overwriting the previous Deploy Configuration section in CLAUDE.md.

Why does my deployment setup prompt for missing production URL values?

The deployment setup prompts for missing values when platform detection cannot find required production URLs or health check endpoints in your existing config files, ensuring complete configuration persistence.