setup-deploy

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill setup-deploy-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/gstack/setup-deploy
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill setup-deploy-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up deployment detection by hand for every project is repetitive, and without a stored configuration, deploy workflows like /land-and-deploy cannot run automatically. This Skill detects your deploy platform, production URL, health checks, and status commands once, then persists everything to CLAUDE.md so future deploys need zero setup. ## Core Features & Use Cases - Platform Detection: Automatically identifies Fly.io, Render, Vercel, Netlify, Heroku, Railway, GitHub Actions deploy workflows, or custom setups by scanning config files like fly.toml, render.yaml, and netlify.toml. - Guided Configuration: Walks through platform-specific setup (app names, CLI checks, inferred URLs) and falls back to interactive questions for custom or manual deploys. - Persistent Config in CLAUDE.md: Writes a Deploy Configuration section covering platform, production URL, merge method, health checks, and pre/post-merge hooks, then verifies the health check URL and status command actually work. - Use Case: You just connected your repo to Render. Run this once, confirm the inferred onrender.com URL, and every future /land-and-deploy run merges, deploys, and polls the health endpoint without asking you anything. ## Quick Start Ask the assistant to run /setup-deploy to detect your deploy 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 scans for platform config files like fly.toml, render.yaml, vercel.json, or netlify.toml, infers your production URL and health check, and writes the full configuration to CLAUDE.md so future deploys run automatically.

Which deploy platforms does setup-deploy detect?

It detects Fly.io, Render, Vercel, Netlify, Heroku, and Railway from their config files, plus GitHub Actions workflows containing deploy or release jobs. If nothing is detected, it asks interactive questions to configure a custom or manual deploy.

Does setup-deploy work without the fly or vercel CLI installed?

Yes. Platform CLIs are optional. If the CLI is missing, the skill falls back to URL-based health checks using curl against the production or health endpoint instead of CLI status commands.

Where is the deployment configuration stored?

All settings live in a Deploy Configuration section inside CLAUDE.md, not a separate config file. Running /setup-deploy again cleanly overwrites the previous section, so reconfiguration is idempotent.

What happens if the health check fails during setup?

The skill reports the failure but does not block. The configuration is still saved to CLAUDE.md, since a temporarily unreachable health endpoint does not invalidate the rest of the deploy settings.