setup-deploy

Detect deployment platforms and health checks, then write configuration to CLAUDE.md.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill setup-deploy-jonkiky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/jonkiky/ccdi-federation-ai/tree/main/.agents/setup-deploy
Command: npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill setup-deploy-jonkiky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often struggle to configure multi-platform deployments. setup-deploy detects target platforms like Fly.io, Render, Vercel, Netlify, Heroku, and GitHub Actions, then collects health checks and deploy status commands to centralize configuration.

Core Features & Use Cases

  • Auto-detect deployment platform signals from project files.
  • Capture production URLs and health check endpoints for reliable monitoring.
  • Write the deployment configuration to CLAUDE.md so future deploys are automatic.
  • Useful for teams migrating to a single source of truth for deployments and saving setup time.

Quick Start

Invoke /setup-deploy to scan your project and write 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 multiple platforms like Fly.io, Vercel, and Render?

Automate deployment configuration by scanning project files like fly.toml, vercel.json, and render.yaml to detect the target platform, production URL, and health check endpoints, then centralize the settings by writing them to CLAUDE.md.

How do I set up health check endpoints and production URLs for future automated deploys?

Set up health check endpoints and production URLs by scanning your project files for platform configuration signals, capturing the deployment details, and writing the centralized configuration to CLAUDE.md for future automated deploys.

Does the deployment setup process support detecting Heroku and Railway platforms from project files?

Yes, deployment setup supports detecting Heroku and Railway platforms by reading project files such as Procfile and railway configuration to identify the target platform, production URL, and health check endpoints automatically.

What is the best way to centralize deployment settings for teams migrating to multiple platforms?

The best way to centralize deployment settings is to auto-detect platform signals from project files, capture production URLs and health check endpoints, and write the resulting configuration to CLAUDE.md to serve as a single source of truth for teams.

Can I use CLAUDE.md to store deployment configuration for GitHub Actions and Netlify?

Yes, you can use CLAUDE.md to store deployment configuration by scanning project files like netlify.toml and GitHub Actions workflows, detecting the target platform, and writing the production URLs and health check endpoints into the file.

Why do I need to write deployment configuration to CLAUDE.md instead of keeping platform-specific files?

Writing deployment configuration to CLAUDE.md centralizes multi-platform settings into a single source of truth, preventing manual reconfiguration and ensuring future deploys run automatically across different platforms without rescanning files.