setup-deploy

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

9|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/CarbeneAI/Forge --skill setup-deploy-carbeneai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/CarbeneAI/Forge/tree/main/.claude/skills/setup-deploy
Command: npx skills add https://github.com/CarbeneAI/Forge --skill setup-deploy-carbeneai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects a project's deployment platform and automates creation of a Deploy Configuration so land-and-deploy workflows run reliably without manual guessing. It saves time by finding platform files, inferring production URLs and health checks, validating status commands, and persisting the results to CLAUDE.md for future automated deploys.

Core Features & Use Cases

  • Platform Detection: Scans for Fly.io, Render, Vercel, Netlify, Heroku, Railway, GitHub Actions workflows, or falls back to a custom/manual prompt flow.
  • Configuration Persistence: Writes a standardized Deploy Configuration section to CLAUDE.md and can overwrite or update existing settings idempotently.
  • Verification & Safety: Validates health-check URLs and deploy status commands, avoids exposing secrets, and supports CLI fallbacks when platform CLIs are available.
  • Use Case: Prepare your web app for automated land-and-deploy by detecting the platform, confirming the production URL, and saving health checks so CI/CD can poll and verify deployments.

Quick Start

Run the /setup-deploy skill to detect your deploy platform, confirm the production URL and health check, 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 automate deployment configuration for Fly.io, Vercel, or Render?

Automate deployment configuration by scanning your project for platform files to infer the production URL and health check endpoints, then persist these settings to CLAUDE.md for reliable CI/CD verification.

What is the best way to set up health check endpoints for automated CI/CD workflows?

Set up health check endpoints by validating production URLs and deploy status commands, ensuring automated land-and-deploy workflows can safely poll and verify deployment success without exposing secrets.

How does platform detection work for web applications without existing deployment settings?

Platform detection works by scanning your project files for recognizable configurations from providers like Fly.io, Render, Vercel, Netlify, Heroku, Railway, or GitHub Actions, falling back to a manual prompt if needed.

Can I use CLI fallbacks to configure deploys if my platform's native integration fails?

Yes, you can use CLI fallbacks to configure deploys when platform CLIs are available, ensuring deploy status commands and health checks remain operational even without native API integrations.

How do I prevent exposing secrets when persisting deploy configuration to CLAUDE.md?

Prevent exposing secrets by validating health check URLs and deploy status commands during configuration, ensuring only safe endpoint definitions are written to the CLAUDE.md file without leaking credentials.

Does this deployment configuration setup support custom or manual workflows outside of standard PaaS providers?

Yes, it supports custom or manual workflows by falling back to interactive prompts when standard platform files are absent, allowing you to define production URLs and health checks for any deployment target.