setup-deploy

You can auto-detect deployment platforms by scanning project files like fly.toml, render.yaml, vercel.json, netlify.toml, and Procfile. The detected configuration is then written directly into CLAUDE.md so future deployments are automatic and require no manual setup.

Yes, deployment automation works with Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom platforms. It scans for platform-specific files to identify your hosting stack and records the correct configuration for one-click reuse.

To persist health-check commands and endpoints, write a Deploy Configuration section into CLAUDE.md. This records the detected platform details and health checks so post-deploy verification runs automatically and reliably on every future deployment.

The best way to reduce setup time is automating platform detection and recording deployment details into CLAUDE.md. This eliminates repetitive manual configuration across environments, reducing setup time from hours to minutes for both solo and team projects.

Yes, you can store custom deployment configuration for GitHub Actions in CLAUDE.md. The detection process scans for workflow files, identifies the custom platform, and persists the deployment details and health checks for automatic one-click reuse.

Health checks often fail after switching platforms because configuration details are not persisted. Writing the detected platform details, endpoints, and health-check commands into CLAUDE.md ensures post-deploy checks are recorded and executed automatically on the new stack.