setup-deploy

Detect deployment platforms and write deployment settings to CLAUDE.md.

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

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

  • Detect deployment platforms across Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom setups.
  • Capture production URLs and health check endpoints to validate deployment readiness.
  • Persist deployment configuration to CLAUDE.md so subsequent deploys are automated and consistent.

Quick Start

Run /setup-deploy to generate deployment settings and write them 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 automate deployment configuration across different platforms?

Deployment configuration is automated by detecting your platform—such as Fly.io, Render, Vercel, Netlify, Heroku, or GitHub Actions—and writing settings to CLAUDE.md for automatic future deploys.

What is CLAUDE.md used for in deployment automation?

CLAUDE.md persists deployment settings like production URLs, health check endpoints, and deploy status commands so subsequent deployments are consistent and fully automated.

Does deployment automation support custom deployment setups?

Yes, deployment detection supports custom setups alongside standard platforms like Vercel, Netlify, and Heroku, capturing production URLs and health check endpoints for any environment.

How do I validate deployment readiness after configuring my platform?

Deployment readiness is validated by capturing health check endpoints and deploy status commands during configuration, which are then recorded in CLAUDE.md to verify successful future deploys.

What's the best way to manage deployment settings for multiple environments?

Managing multi-environment deployment settings is handled by detecting platform-specific configurations, production URLs, and health check endpoints, then persisting them to CLAUDE.md for consistent automated deploys.

Why does my deployment platform need to be detected before automating deploys?

Platform detection is required to identify the correct deploy status commands and health check endpoints, ensuring the configuration written to CLAUDE.md accurately matches your specific deployment environment.