replit-prod-checklist
Execute Replit production deployment checklist with rollback and health monitoring. Use when deploying Replit apps to production, preparing for launch, or implementing go-live procedures with Autoscale or Reserved VM. Trigger with phrases like "replit production", "deploy replit", "replit go-live", "replit launch checklist", "replit prod ready". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill replit-prod-checklist --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Replit Production Checklist ## Overview Complete checklist for deploying Replit apps to production using Autoscale or Reserved VM deployments. Covers configuration, secrets, health checks, custom domains, rollback procedures, and monitoring. ## Prerequisites - Replit Core, Pro, or Teams plan (deployment access) - App tested and working in Workspace - PostgreSQL database provisioned (if needed) -
What does the replit-prod-checklist skill do?
Execute Replit production deployment checklist with rollback and health monitoring. Use when deploying Replit apps to production, preparing for launch, or implementing go-live procedures with Autoscale or Reserved VM. Trigger with phrases like "replit production", "deploy replit", "replit go-live", "replit launch checklist", "replit prod ready". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill replit-prod-checklist --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
