setup-deploy

Detect deployment platforms and persist deployment configuration to CLAUDE.md.

1|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill setup-deploy-concept2cure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/concept2cure/ClinicalSageAI-2-replit/tree/main/.claude/skills/gstack/setup-deploy
Command: npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill setup-deploy-concept2cure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic.

Core Features & Use Cases

  • Platform detection across multiple providers (Fly.io, Render, Vercel, Netlify, Heroku, Railway, custom) and auto-detection of production URL.
  • Interactive setup to tailor health checks, deploy status commands, merge strategy, and project type.
  • Idempotent CLAUDE.md updates so re-running /setup-deploy updates configuration without duplicating data.

Quick Start

Run the setup-deploy skill to generate deployment configuration and persist it 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 CI/CD deployment settings for multiple platforms like Vercel, Fly.io, and Render?

To configure CI/CD deployment settings, this setup detects your deployment platform, production URL, and health check endpoints, then interactively guides you through tailoring merge strategies and deploy status commands before persisting the configuration to CLAUDE.md.

What is the best way to automate saving deployment configuration without duplicating data in CLAUDE.md?

Automating deployment configuration requires an idempotent setup process that re-reads CLAUDE.md on subsequent runs to safely update existing platform specifics and health checks without duplicating data.

How do I set up health check endpoints and deploy status commands for an automated release workflow?

To set up health check endpoints and deploy status commands, run the interactive setup flow which detects your platform specifics and project type, persisting the tailored release workflow configuration directly into CLAUDE.md.

Does the deployment setup support custom platforms and auto-detection of production URLs?

Yes, the deployment setup supports custom platforms alongside providers like Heroku, Railway, and Netlify, featuring auto-detection of your production URL to ensure future automated deploys function correctly.

Can I re-run setup to update deployment configuration if my merge strategy or project type changes?

Yes, you can re-run the setup because it is designed to be idempotent and safe, re-reading CLAUDE.md on subsequent runs to update your merge strategy, project type, and platform specifics without duplicating data.

Why do I need to persist deploy configuration to CLAUDE.md for future releases?

Persisting deploy configuration to CLAUDE.md is necessary so that all future automated deploys within the land-and-deploy workflows remember your platform specifics, health checks, and deploy status commands without requiring manual reconfiguration.