setup-deploy

Detect deployment platforms, infer health checks, and write Deploy Configuration to CLAUDE.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detecting deployment platform details, health checks, and status commands is repetitive and error-prone across projects. This Skill centralizes detection, verification, and persistent configuration so future deploys run automatically via /land-and-deploy.

Core Features & Use Cases

  • Platform detection: Scans for fly.toml, render.yaml, vercel config, netlify.toml, Procfile, GitHub Actions workflows, and common project markers.
  • Inference & verification: Infers production URL and status commands, checks CLI availability, and validates health endpoints without exposing secrets.
  • Write-to-source: Persists a clear Deploy Configuration section into CLAUDE.md so CI/CD automation can read it.
  • Use case: Run this on a repo with a PR ready to merge so /land-and-deploy can merge, wait for deploy, and verify via a saved health check.

Quick Start

Run /setup-deploy, confirm the detected platform and production URL, and accept to save the Deploy Configuration into 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 automated deployment settings for a new repository?

To configure automated deployment settings, this Skill scans your repository for platform config files like fly.toml or netlify.toml, infers production URLs, validates health check endpoints, and writes a persistent Deploy Configuration section into CLAUDE.md.

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

Yes, deployment automation works with Fly.io, Render, Vercel, Netlify, Heroku, and GitHub Actions by detecting platform-specific configuration files and generating the appropriate health check and status commands for each environment.

What's the best way to set up health check endpoints without exposing secrets?

The best way to set up health check endpoints safely is by inferring the production URL and validating the health endpoint status without exposing secrets, then persisting the verified configuration into CLAUDE.md for automated workflows.

How do I detect which deployment platform a project is using?

You can detect the deployment platform by scanning the repository for specific markers and config files such as fly.toml, render.yaml, vercel config, netlify.toml, Procfile, and GitHub Actions workflows.

Why do I need to add a Deploy Configuration section to CLAUDE.md?

You need a Deploy Configuration section in CLAUDE.md so CI/CD automation can read the platform details, production URLs, and health check commands, enabling future automated merge and deploy workflows to run without manual intervention.

Can I use GitHub Actions workflows for deploy automation if I have a custom target?

Yes, you can use GitHub Actions workflows for deploy automation with custom targets; the Skill detects GitHub Actions configurations alongside standard platform files and applies the inferred deployment settings accordingly.