setup-deploy

Detect deployment platforms and write health-check configuration to CLAUDE.md.

1|Updated Apr 15, 2026

Search Tags:#automation #deploy #CLAUDE.md #workflows #platform-detection #gstack

Ready to run

npx skills add https://github.com/tyhuffman7/gstack-hermes --skill setup-deploy-tyhuffman7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/tyhuffman7/gstack-hermes/tree/main/gstack-setup-deploy
Command: npx skills add https://github.com/tyhuffman7/gstack-hermes --skill setup-deploy-tyhuffman7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying gstack across multiple platforms is tedious and error-prone. This skill automates platform detection (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, or custom) and records the discovered deployment configuration into CLAUDE.md so future deployments are automatic and reliable.

Core Features & Use Cases

Detects deployment targets by scanning project files (fly.toml, render.yaml, vercel.json, netlify.toml, Procfile, railway config) and identifying the correct hosting stack.
Updates CLAUDE.md with a Deploy Configuration section to persist platform, health checks, and environment details for one-click future deployments.
Works in team or solo projects and reduces setup time for new environments to minutes rather than hours.

Quick Start

Run /setup-deploy in your project to begin automatic detection and CLAUDE.md configuration.

Frequently Asked Questions about setup-deploy

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

FAQPage Schema

How do I auto-detect project deployment platforms and save the configuration?▼

You can auto-detect deployment platforms by scanning project files like fly.toml, render.yaml, vercel.json, netlify.toml, and Procfile. The detected configuration is then written directly into CLAUDE.md so future deployments are automatic and require no manual setup.

Does deployment automation work with Fly.io, Render, Vercel, and Netlify?▼

Yes, deployment automation works with Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom platforms. It scans for platform-specific files to identify your hosting stack and records the correct configuration for one-click reuse.

How do I persist health-check commands and endpoints for automatic post-deploy verification?▼

To persist health-check commands and endpoints, write a Deploy Configuration section into CLAUDE.md. This records the detected platform details and health checks so post-deploy verification runs automatically and reliably on every future deployment.

What's the best way to reduce manual setup time when deploying across multiple hosting platforms?▼

The best way to reduce setup time is automating platform detection and recording deployment details into CLAUDE.md. This eliminates repetitive manual configuration across environments, reducing setup time from hours to minutes for both solo and team projects.

Can I use CLAUDE.md to store custom deployment configuration for GitHub Actions?▼

Yes, you can store custom deployment configuration for GitHub Actions in CLAUDE.md. The detection process scans for workflow files, identifies the custom platform, and persists the deployment details and health checks for automatic one-click reuse.

Why are my deployment health checks failing after switching hosting platforms?▼

Health checks often fail after switching platforms because configuration details are not persisted. Writing the detected platform details, endpoints, and health-check commands into CLAUDE.md ensures post-deploy checks are recorded and executed automatically on the new stack.