setup-deploy

Detect hosting platforms and write deployment configuration to CLAUDE.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Landing new deployments often require manual setup to align hosting platforms, URLs, health checks, and deploy status, leading to inconsistent configurations and slower rollouts.

Core Features & Use Cases

  • Platform detection: identifies Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, or custom pipelines to tailor deployment steps.
  • CLAUDE.md synchronization: writes deployment configuration to CLAUDE.md so future deploys are automatic.
  • Health checks and status: validates health endpoints and provides deploy-status commands to monitor progress.
  • Real-world use: after changing hosting, run setup-deploy to reconfigure your land-and-deploy settings across environments.

Quick Start

Run setup-deploy to generate and apply deployment configuration for your project.

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 hosting platforms and configure deployment settings?

To automatically configure deployment settings, you can run a setup process that detects hosting platforms like Fly.io, Render, or Vercel. It identifies production URLs and health checks, then writes the configuration to CLAUDE.md for future reuse.

What is the best way to synchronize deployment configurations across environments after changing hosting?

Synchronizing deployment configurations across environments is achieved by writing hosting platform details, production URLs, and health checks into CLAUDE.md. Running a setup command reconfigures your land-and-deploy settings to keep all environments aligned.

Does this deployment automation work with GitHub Actions and custom pipelines?

Yes, this deployment automation works with GitHub Actions and custom pipelines alongside platforms like Netlify and Heroku. It detects the specific pipeline in use and tailors the deployment steps and status commands to match your hosting environment.

How do I validate health endpoints and get deploy status commands during a rollout?

To validate health endpoints and get deploy status commands, the deployment setup process checks your health endpoints and generates specific status commands. These commands allow you to monitor deployment progress and verify production URL availability.

Why do my land-and-deploy rollouts require manual setup and produce inconsistent configurations?

Land-and-deploy rollouts require manual setup because hosting platforms, URLs, and health checks are not persisted. Automatically detecting these settings and writing them to CLAUDE.md ensures consistent configurations and eliminates manual alignment for future deploys.