setup-deploy

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

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill setup-deploy-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/team/setup-deploy
Command: npx skills add https://github.com/ajsai47/holyclaude --skill setup-deploy-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, error-prone work of manually configuring deployment settings for different platforms, saving you hours of repetitive setup and ensuring your /land-and-deploy workflow works automatically on the first run.

Core Features & Use Cases

  • Multi-platform auto-detection: Automatically identifies your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, or custom) by scanning for platform-specific config files and CI/CD workflow definitions.
  • Auto-inferred deployment settings: Pulls production URLs, health check endpoints, and deploy status commands directly from your project config, no manual data entry required.
  • Persistent CLAUDE.md configuration: Writes all confirmed deployment settings to your project's CLAUDE.md file as the source of truth, so /land-and-deploy uses them automatically for every future deploy with no repeated setup.
  • Use Case: You just deployed a new web app to Fly.io. Run this Skill once, and it detects your fly.toml, confirms your app's production URL, sets up health checks, and saves all config to CLAUDE.md so you never have to manually enter deploy settings again.

Quick Start

Ask the Skill to configure deployment for your current project, review and confirm the auto-detected platform, URL, and health check settings when prompted, and it will save all configuration to CLAUDE.md for fully automatic future deploys.

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 platforms like Vercel and Fly.io?

Deployment configuration is automated by scanning your project for platform-specific config files like fly.toml, auto-inferring production URLs and health check endpoints, and persisting settings to CLAUDE.md for repeatable deploys.

How does CLAUDE.md store deploy settings for CI/CD pipelines?

CLAUDE.md stores deploy settings by recording confirmed platform detection results, production URLs, and deploy status commands as the source of truth, enabling downstream deploy automation tools to execute fully automated workflows.

Can I use this to detect custom deploy pipelines and GitHub Actions workflows?

Yes, platform detection scans for CI/CD workflow definitions and custom deploy pipeline configurations, automatically inferring the necessary health check endpoints and deploy status commands without manual data entry.

What is the best way to set up zero-friction deploys on Render or Netlify?

Zero-friction deploys are set up by running auto-configuration once to detect your Render or Netlify config files, confirming the auto-inferred deployment settings, and saving them to CLAUDE.md for all future automated deploys.

Do I need to manually enter production URLs and health check endpoints for Heroku deploys?

No manual data entry is required. Deployment settings including production URLs and health check endpoints are pulled directly from your project configuration files and saved to CLAUDE.md after confirmation.

Why does my land-and-deploy workflow require repeated manual setup?

Repeated manual setup occurs because deployment settings are not persisted. Saving confirmed platform configurations to CLAUDE.md ensures your land-and-deploy workflow operates automatically on the first run and every future deploy.