setup-deploy

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates the detection and configuration of deployment settings so that the gstack /land-and-deploy workflow can run without manual setup.

Core Features & Use Cases

  • Detects the hosting platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, or custom) by reading common config files.
  • Determines the production URL, health‑check endpoint, and status commands.
  • Writes a unified “## Deploy Configuration” section to CLAUDE.md for future automated deployments.
  • Prompts the user for missing information and respects existing configurations, making the process idempotent.

Quick Start

Run /setup-deploy to automatically detect and configure your deployment.

Frequently Asked Questions about setup-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure automatic deployment settings for a gstack project?

To configure deployment for a gstack project, run /setup-deploy to automatically detect your hosting platform, production URL, and health checks, then write them to CLAUDE.md.

What hosting platforms can be automatically detected for deployment configuration?

Deployment configuration can automatically detect Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, or custom hosting platforms by reading their common config files.

How does CLAUDE.md store deployment configuration for land-and-deploy workflows?

CLAUDE.md stores deployment configuration by appending a unified 'Deploy Configuration' section containing the production URL, health-check endpoint, and status commands for automated workflows.

Do I need to manually provide missing deployment details during setup?

You need to manually provide missing deployment details only when automatic detection fails; the setup process prompts you for missing information while respecting existing configurations.

Can I rerun deployment setup without duplicating configuration in CLAUDE.md?

You can rerun deployment setup without duplicating configuration because the process is idempotent, meaning it respects existing configurations and updates CLAUDE.md safely.

What repository files are required to detect platform configuration automatically?

Detecting platform configuration requires access to repository files such as platform-specific config files and the ability to update CLAUDE.md with the detected deployment settings.