release

Verifies build readiness and generates render.yaml or vercel.json deployment configuration.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill release-leroyadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/release
Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill release-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing a project for deployment to Render or Vercel involves checking build commands, start commands, output directories, environment variables, and health checks, which is error-prone when done manually. This Skill inspects the project, verifies local readiness, and produces correct provider configuration without performing any external deploy action. ## Core Features & Use Cases - Project Inspection: Reads plans, package files, framework config, and git state to identify app type, build/start commands, runtime needs, and required env var names. - Readiness Verification: Runs local, non-destructive checks such as build, test, and smoke tests against a health path, reporting gaps instead of guessing. - Config Generation: Creates or updates render.yaml or vercel.json only when defaults are insufficient, including service type, build command, health check path, and env var names without values. - Use Case: After finishing a Next.js feature, run /release vercel to confirm the build passes, list required env vars, and get a release packet with the exact next deployment step. ## Quick Start Ask the assistant to run /release to check deployment readiness and prepare Render or Vercel configuration for this project.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a project for deployment to Render or Vercel?▼

Run /release with an optional target argument like render or vercel. The skill reads project plans and package files, verifies build and start commands locally, and produces a release packet with config changes, env var names, and next steps.

When should I use render.yaml versus vercel.json?▼

Use render.yaml when the app needs repeatable setup or multiple services like web services, workers, or cron jobs. Create vercel.json only when Vercel defaults are insufficient, since many Vercel projects need no config file at all.

Does the release skill deploy my app automatically?▼

No. The skill stops before any external deploy, remote service creation, remote env change, push, or publish unless you explicitly approve in the current chat. It only inspects, runs local checks, and edits local config files.

Which apps fit Render versus Vercel deployment?▼

Long-running workers and background jobs usually fit Render better, while frontend Next.js or Astro sites usually fit Vercel well. The skill states plainly when a provider is a poor fit and recommends the better target.

What happens if my build command or env vars are missing?▼

The skill reports the gap instead of inventing certainty. If a check needs secrets, it lists the required env var names and skips that check, and blockers are surfaced in the final release packet.