setup-deploy

Detect deployment platforms and write deploy configuration into CLAUDE.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns deployment setup from a manual guessing game into a repeatable configuration step. It identifies where the app is deployed, how to check it, and how to store that knowledge so future deploys do not need rediscovery.

Core Features & Use Cases

  • Platform detection: Recognizes common deployment targets like Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom flows.
  • Deploy metadata capture: Collects the production URL, health check path, deploy status command, and merge method, then writes them into CLAUDE.md.
  • Operational follow-through: Handles existing config, asks for missing details, and supports one-time setup for teams that want /land-and-deploy to work automatically.
  • Use case: A builder inherits a Next.js app with no deployment notes. This Skill figures out the platform and leaves behind the deploy instructions so the next person can ship without spelunking.

Quick Start

Ask the setup-deploy skill to detect your deployment platform and write the production URL, health check, and status command into 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 configure deployment settings for Vercel or Fly.io and save them to CLAUDE.md?

Deployment configuration involves detecting the platform, collecting the production URL and health check path, and writing the deploy status commands and post-deploy verification steps into CLAUDE.md for future automated releases.

What is the best way to document manual release flows and deploy health checks for a web app?

Documenting manual release flows involves detecting the deployment target, capturing the production URL and health check endpoint, and recording the status command and merge method in CLAUDE.md.

Does this deployment setup tool support GitHub Actions and Render?

Yes, deployment configuration supports GitHub Actions and Render, alongside Fly.io, Vercel, Netlify, Heroku, and custom manual flows, capturing deploy metadata for each platform.

Can I add post-deploy verification and health checks to an existing deployment configuration?

Yes, the deployment configuration process handles existing setups, asks for missing details like the health check path, and updates CLAUDE.md with post-deploy verification steps and status commands.

Why do I need to write deploy status commands and merge behavior into CLAUDE.md?

Writing deploy status commands and merge behavior into CLAUDE.md turns deployment setup into a repeatable step, ensuring future deploys execute automatically without manual rediscovery of platform details.

What are the limitations of using CLAUDE.md for deployment metadata capture?

The limitation of capturing deployment metadata in CLAUDE.md is that it requires manual input for missing details when the platform cannot be automatically detected, especially for custom manual release flows.