Setup Deploy

What Is This?

Overview

Setup Deploy is a configuration skill within the gstack toolkit that detects and records your deployment platform settings so that future deployments run automatically without manual intervention. When you invoke this skill, it identifies your deploy platform, production URL, health check endpoints, and deploy status commands, then writes all of this information to your project's CLAUDE.md file for persistent use.

The skill supports a wide range of deployment platforms including Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom deployment pipelines. Rather than requiring you to re-enter configuration details each time you deploy, Setup Deploy captures that information once and makes it available to the land-and-deploy workflow on every subsequent run.

This approach eliminates a common friction point in development workflows: the gap between writing code and shipping it. By establishing a reliable configuration baseline, Setup Deploy ensures that your deployment process is consistent, repeatable, and aligned with your specific infrastructure from the first run onward.

Who Should Use This

• Developers integrating gstack into a new project who need to configure their deployment target before using land-and-deploy
• Teams adopting a standardized deployment workflow across multiple projects and environments
• Engineers working with multiple platforms who want a single configuration step rather than repeated manual setup
• Solo developers who want to reduce cognitive overhead by automating deployment configuration
• DevOps practitioners setting up CI/CD pipelines that rely on gstack for deployment orchestration
• Anyone who has previously run land-and-deploy without a configuration file and encountered missing or incorrect deployment settings

Why Use It?

Problems It Solves

• Eliminates the need to manually specify deployment targets, URLs, and health check paths every time you run a deploy command
• Removes ambiguity about which platform a project deploys to, especially in repositories that contain configuration files for multiple platforms
• Prevents deployment failures caused by missing or incorrect environment-specific settings that were never formally recorded
• Reduces onboarding time for new contributors who need to understand how a project deploys without reading scattered documentation
• Resolves inconsistencies between local deployment commands and CI/CD pipeline behavior by establishing a single source of truth in CLAUDE.md

Core Highlights

• Automatic platform detection across Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom targets
• Writes configuration persistently to CLAUDE.md so all future deploys are automatic
• Captures production URL for post-deploy verification steps
• Records health check endpoint paths for automated readiness confirmation
• Stores deploy status commands for monitoring deployment progress
• Works as a one-time setup step that integrates cleanly into existing gstack workflows
• Supports custom deployment pipelines beyond the named platform presets
• Designed to work alongside land-and-deploy without requiring additional tooling

How to Use It?

Basic Usage

Invoke Setup Deploy by describing your intent in natural language within your gstack-enabled environment:

setup deploy
configure deployment
set up land-and-deploy

The skill will prompt you for or automatically detect the relevant settings and write them to your project's CLAUDE.md file:

## Deployment Configuration
- Platform: fly.io
- Production URL: https://myapp.fly.dev
- Health Check: /health
- Deploy Command: fly deploy
- Status Command: fly status

Specific Scenarios

Scenario 1: New project on Fly.io You have a new application and want to configure it for deployment. Run "setup deploy" and the skill detects your fly.toml file, extracts the app name and region, and writes the appropriate configuration to CLAUDE.md automatically.

Scenario 2: Custom deployment pipeline Your project uses a custom shell script for deployment. Provide the deploy command path and health check URL manually, and Setup Deploy records these as custom platform settings that land-and-deploy will use on every subsequent run.

Real-World Examples

A team using Vercel for a Next.js application runs Setup Deploy once during project initialization. From that point forward, every developer on the team can run land-and-deploy without needing to know the Vercel project ID or production domain.

A solo developer maintaining three separate services on Render configures each repository independently using Setup Deploy. Each CLAUDE.md file contains the correct service-specific settings, preventing cross-project configuration errors.

Important Notes

Requirements

• A gstack-enabled environment with access to CLAUDE.md read and write permissions
• At least one recognized deployment platform configuration file present in the repository, or manual input for custom platforms
• The land-and-deploy skill installed and available if you intend to use the written configuration immediately
• Sufficient project context for the skill to detect platform-specific files such as fly.toml, render.yaml, vercel.json, or netlify.toml