setup-deploy

Detects deploy platform and writes deployment configuration to CLAUDE.md for automated deploys.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/westkite1201/garden-engine --skill setup-deploy-westkite1201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/westkite1201/garden-engine/tree/main/.claude/skills/gstack/setup-deploy
Command: npx skills add https://github.com/westkite1201/garden-engine --skill setup-deploy-westkite1201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually configuring deployment settings for every project is repetitive and error-prone. This Skill automatically detects your deploy platform, production URL, health checks, and status commands, then persists everything to CLAUDE.md so future deploys via /land-and-deploy run without re-detection. ## Core Features & Use Cases - Platform Detection: Scans for fly.toml, render.yaml, vercel.json, netlify.toml, Procfile, railway configs, and GitHub Actions deploy workflows to identify your hosting platform. - Guided Configuration: Walks through platform-specific setup for Fly.io, Render, Vercel, Netlify, Heroku, or custom/manual deploys, including health check endpoints and deploy status commands. - Persistent Config: Writes a structured "Deploy Configuration" section to CLAUDE.md covering platform, production URL, merge method, and pre/post-deploy hooks. - Use Case: After adding a fly.toml to your project, run this Skill once; it detects Fly.io, infers your app URL, verifies the health endpoint, and saves the config so every future merge deploys automatically. ## Quick Start Ask the assistant to run /setup-deploy to detect my deployment platform and save the configuration 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 automatic deployment for my project?

Run /setup-deploy once. It detects your platform from config files like fly.toml or render.yaml, asks you to confirm the production URL and health checks, then writes everything to CLAUDE.md so /land-and-deploy works automatically afterward.

What deployment platforms does setup-deploy detect?

It detects Fly.io, Render, Vercel, Netlify, Heroku, and Railway via their config files, plus GitHub Actions deploy workflows. If nothing is detected, it falls back to a guided questionnaire for custom or manual deploy setups.

Does setup-deploy work without platform CLIs installed?

Yes. Platform CLIs like fly or vercel are optional. If a CLI is missing, the Skill falls back to URL-based health checks and HTTP polling instead of CLI status commands.

Can I reconfigure deployment settings after running setup-deploy?

Yes. Running /setup-deploy again detects the existing configuration in CLAUDE.md and offers to reconfigure from scratch, edit specific fields, or keep the current settings. It overwrites the previous config cleanly.

Where does setup-deploy store the deployment configuration?

All settings are stored in a "Deploy Configuration" section of CLAUDE.md in your project root. This file is the single source of truth that /land-and-deploy reads on every run.