setup-deploy

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

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/dhnpmp-tech/project-agent --skill setup-deploy-dhnpmp-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/dhnpmp-tech/project-agent/tree/main/.claude/skills/gstack/setup-deploy
Command: npx skills add https://github.com/dhnpmp-tech/project-agent --skill setup-deploy-dhnpmp-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually figuring out how a project deploys — which platform, what URL, how to verify success — is repetitive detective work that must be redone every time an automated deploy workflow runs. This Skill detects the deployment setup once and persists it to CLAUDE.md so future deploys run automatically. ## Core Features & Use Cases - Platform Detection: Scans for Fly.io, Render, Vercel, Netlify, Heroku, Railway config files and GitHub Actions deploy workflows to identify the hosting platform. - Configuration Persistence: Writes platform, production URL, health check endpoint, deploy status command, and merge method into a ## Deploy Configuration section in CLAUDE.md. - Verification: Tests the configured health check URL and deploy status command after writing, reporting reachability without blocking. - Use Case: A developer with a Fly.io app runs the skill once; it reads fly.toml, infers the production URL, saves the config, and every subsequent /land-and-deploy run skips detection entirely. ## Quick Start Ask the assistant to run /setup-deploy to detect your 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 detection for my project?

Run the setup-deploy skill once. It scans for platform config files like fly.toml, render.yaml, vercel.json, and netlify.toml, detects your production URL and health checks, then writes everything to a Deploy Configuration section in CLAUDE.md.

What deployment platforms does setup-deploy support?

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 interactive questions 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 not installed, the skill falls back to URL-based health checks instead of CLI status commands, so configuration still completes.

What happens if I run setup-deploy more than once?

The skill is idempotent. It detects the existing Deploy Configuration section in CLAUDE.md, shows it to you, and offers to reconfigure from scratch, edit specific fields, or keep the current settings.

Does setup-deploy expose API keys or secrets?

No. The skill explicitly avoids printing full API keys, tokens, or passwords. For example, when checking for a Render API key it only displays the first four characters to confirm presence.