setup-deploy

Detect deployment platforms and write Deploy Configuration to CLAUDE.md.

Updated Dec 22, 2019
One-click install
npx skills add https://github.com/sajalsuhane/sajalsuhane.github.io --skill setup-deploy-sajalsuhane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/sajalsuhane/sajalsuhane.github.io/tree/main/.claude/skills/gstack/setup-deploy
Command: npx skills add https://github.com/sajalsuhane/sajalsuhane.github.io --skill setup-deploy-sajalsuhane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure and persist deployment settings for /land-and-deploy so your project can automatically deploy to the detected platform with correct production URL, health checks, and deploy status commands.

Core Features & Use Cases

  • Platform detection across Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom setups.
  • Production URL inference and health-check endpoint configuration.
  • Writes the Deploy Configuration section to CLAUDE.md to ensure future deployments are consistent.
  • Use during initial setup, reconfiguration after changes, or team handoff to lock in deployment workflows.

Quick Start

Run /setup-deploy to detect your deployment platform, confirm the production URL, and persist 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 automate deployment configuration for multiple hosting platforms?

Automated deployment configuration detects platform files for Fly.io, Render, Vercel, Netlify, Heroku, and GitHub Actions, then writes validated settings to CLAUDE.md. It reads repository signals to infer production URLs and health-check endpoints for consistent future deployments.

Does deployment setup support Fly.io and Render for automated health checks?

Yes, deployment setup supports Fly.io and Render alongside Vercel, Netlify, Heroku, and GitHub Actions. It validates platform files and configures health-check endpoints, writing the production URL and deploy status commands directly to CLAUDE.md.

How does CLAUDE.md store deploy configuration for gstack workflows?

CLAUDE.md stores deploy configuration by appending a Deploy Configuration section containing the detected platform, production URL, and health-check settings. This ensures land-and-deploy workflows read consistent instructions for future automated deployments.

What is the best way to configure production URLs and deploy status commands?

The best way to configure production URLs and deploy status commands is running an automated setup that detects your platform and persists settings to CLAUDE.md. This reads repository signals to infer the URL and validate platform files for future deployments.

Can I reconfigure deployment settings after changing my hosting platform?

Yes, you can reconfigure deployment settings after platform changes by rerunning setup to detect the new environment. It reads updated repository signals, validates the new platform files, and overwrites the CLAUDE.md Deploy Configuration section.

Why does land-and-deploy need a CLAUDE.md configuration file?

Land-and-deploy needs a CLAUDE.md configuration file to read persisted deployment settings including platform, production URL, and health-check endpoints. Without this validated configuration section, automated workflows lack the necessary instructions to deploy consistently.