setup-deploy

Detect deployment platforms and write verified deploy configuration to CLAUDE.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often lack a single canonical deploy configuration and it is tedious to discover the platform, production URL, health checks, and status commands by hand; this Skill automates detection, prompts for confirmations, and persists a verified deploy config to CLAUDE.md so future deploys are automatic.

Core Features & Use Cases

  • Platform detection: Scans for Fly.io, Render, Vercel, Netlify, Heroku, Railway, GitHub Actions, and custom deploy patterns.
  • Safe configuration writing: Shows detected values, asks the user to confirm before writing the ## Deploy Configuration section into CLAUDE.md.
  • Verification & fallbacks: Attempts HTTP health checks and CLI status commands when available and records deploy status commands for /land-and-deploy.
  • Use case: Turn a repo with a fly.toml or GitHub Actions deploy workflow into an automatically verifiable deployment target for continuous land-and-deploy flows.

Quick Start

Run /setup-deploy to detect your deploy platform, confirm the production URL and health checks, and save the deploy 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 automatically detect deployment settings for Vercel, Fly.io, and GitHub Actions?

You can automatically detect deployment settings by scanning your repository for platform-specific files like fly.toml or GitHub Actions workflows, then writing the verified production URL and health check commands into CLAUDE.md.

What's the best way to configure health checks for a continuous deployment workflow?

Configuring health checks for continuous deployment involves detecting your deploy platform, attempting HTTP health checks or CLI status commands, and persisting those verified status commands into CLAUDE.md for automated future verification.

Does this deployment platform detection work with Render, Netlify, and Heroku?

Yes, deployment platform detection works with Render, Netlify, Heroku, Railway, Vercel, Fly.io, and custom deploy patterns by scanning your repository to identify the active platform and extract its configuration.

How do I save deploy configuration safely without exposing secrets?

To save deploy configuration safely, the system shows all detected values and prompts for user confirmation before writing the production URL, health check, and deploy status commands into CLAUDE.md, ensuring safe handling of secrets.

Can I verify a deployment status automatically after detecting the platform?

Yes, you can verify deployment status automatically by running available HTTP health checks and CLI status commands after platform detection, recording those commands in CLAUDE.md for subsequent land-and-deploy flows.

Why do I need to write deploy configuration to CLAUDE.md?

Writing deploy configuration to CLAUDE.md creates a single canonical source for your production URL and status commands, eliminating the need to manually discover platform settings and enabling automatic future deploys.