setup-deploy

Detect deployment platforms and persist settings to CLAUDE.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually configuring deployment settings for every project is tedious and error-prone. This Skill automatically detects your deployment platform, production URL, health checks, and status commands, then persists them to CLAUDE.md so future deploys work without repeated setup.

Core Features & Use Cases

  • Platform Detection: Automatically identifies Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, or custom platforms by scanning config files.
  • Health Check Configuration: Detects or helps you define health check endpoints for reliable deploy monitoring.
  • Persistent Configuration: Writes all settings to CLAUDE.md so /land-and-deploy skips detection on subsequent runs.
  • Use Case: You just pushed a new project to GitHub and want to deploy it. Instead of manually looking up platform-specific config formats, you run this Skill once and it figures out your Render or Vercel setup and stores it.

Quick Start

Use the setup-deploy skill to automatically detect your deployment platform and write the 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, Render, or Vercel projects?

You can automate deployment configuration by scanning project files to detect your target platform, production URL, and health check endpoints, then persisting these settings to enable future automated deployments.

What is the best way to persist deployment settings for CI/CD pipelines?

Persisting deployment settings involves writing detected platform configurations, health checks, and deploy status commands to CLAUDE.md, allowing subsequent automated deployments to skip manual detection steps.

Does this deployment setup work with GitHub Actions and Heroku?

Yes, the deployment setup detects configurations across GitHub Actions and Heroku, along with Fly.io, Render, Vercel, Netlify, and custom environments by scanning your existing project configuration files.

How do I configure health check endpoints for automated deployment monitoring?

Configuring health check endpoints is handled automatically by detecting existing settings or helping you define them during the initial deployment configuration scan for reliable monitoring.

Why does my deployment platform detection fail on subsequent runs?

Platform detection should only run once because the detected deployment settings are persisted to CLAUDE.md, ensuring future automated deployments skip the detection phase entirely.

Can I use this to detect custom deployment environments outside of standard platforms?

Yes, you can detect custom deployment environments alongside standard platforms like Vercel and Netlify by scanning your project configuration files for specific environment settings.