setup-deploy

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

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill setup-deploy-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/setup-deploy
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill setup-deploy-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually configuring deployment settings for every project is repetitive and error-prone. This Skill auto-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 automatically without re-detection. ## Core Features & Use Cases - Platform Auto-Detection: Scans for fly.toml, render.yaml, vercel.json, netlify.toml, Procfile, railway config, 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 in CLAUDE.md: Writes a structured Deploy Configuration section covering platform, production URL, merge method, and pre/post-deploy hooks, verified with a live health check curl. - Use Case: You just connected a repo to Render. Run the skill once, it detects render.yaml, infers the onrender.com URL, confirms with you, and saves the config so every future merge deploys and verifies automatically. ## Quick Start Ask the assistant to set up deployment configuration for this project by running the setup-deploy skill.

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 the setup-deploy skill once. It detects your platform from config files like fly.toml or render.yaml, asks you to confirm the production URL and health check, then writes the configuration to CLAUDE.md for all future deploys.

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 using curl against the production endpoint instead of CLI status commands.

Where is the deploy configuration stored?

All configuration lives in a Deploy Configuration section inside the project's CLAUDE.md file. There is no separate config file, and re-running the skill cleanly overwrites the previous section.

Why does my deploy health check fail after setup?

Health checks fail when the production URL is unreachable, the app is still deploying, or the endpoint path is wrong. The skill reports the failure but still saves the config, since temporary unreachability does not invalidate the settings.