setup-deploy

Detect deployment platforms and configure automated deploy verification in CLAUDE.md.

8|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/MFS-code/gstack --skill setup-deploy-mfs-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/MFS-code/gstack/tree/main/setup-deploy
Command: npx skills add https://github.com/MFS-code/gstack --skill setup-deploy-mfs-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the guesswork and manual setup needed to make /land-and-deploy work by detecting your deployment platform, finding a production URL, and defining how to verify deploy success.

Core Features & Use Cases

  • Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions workflows, or custom/manual setups).
  • Captures deploy verification details by identifying a production URL and either a health-check endpoint (URL-based) or a deploy-status command (CLI-based).
  • Persists configuration for future runs by writing everything into CLAUDE.md so deployment setup happens once and subsequent deploys are automatic.
  • Use Case: You have a PR ready and want /land-and-deploy to merge and verify on your hosting provider; you run /setup-deploy once to create the correct configuration.

Quick Start

Type /setup-deploy and answer the prompts to confirm your platform, production URL, and how to check that a deployment succeeded.

Frequently Asked Questions about setup-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure automated deploy verification for a web project?

To configure automated deploy verification, you run a setup process that detects your deployment platform and identifies a production URL or health-check endpoint to confirm successful releases. This configuration is then persisted into your project's CLAUDE.md file for future automated use.

Does automated deployment configuration support Fly.io, Render, and Vercel?

Yes, automated deployment configuration supports Fly.io, Render, Vercel, Netlify, Heroku, and GitHub Actions workflows. It detects existing platform configuration files to automatically capture the correct deployment trigger and production URL for your specific hosting provider.

How do I set up deployment health checks for a custom hosting workflow?

You can set up deployment health checks for custom workflows by specifying a CLI-based deploy-status command or a URL-based health-check endpoint. When no known platform configuration files are found, the setup process prompts you to manually define these verification details.

Why do I need a CLAUDE.md file for deployment automation?

You need a CLAUDE.md file for deployment automation because it persists your deploy configuration, including the production URL, deploy trigger, and health-check details. Writing this metadata once ensures subsequent automated deployments run correctly without requiring manual setup each time.

Can I use CI/CD platform detection without exposing deployment secrets?

Yes, you can use CI/CD platform detection safely without exposing secrets. The generated deploy configuration includes specific safety guidelines to ensure sensitive credentials remain protected while capturing your production URL and deploy verification commands.