Document how your app is deployed

Name: Document how your app is deployed
Author: @slashclone

@slashclone/deploy-guide

Write a deploy guide so anyone on your team can ship a release, see what is live, and roll back. It reads your repo and fills docs/DEPLOY.md with hosts and domains, env var names per environment, first-time setup, the release pipeline, rollback steps, and a dev versus production differences table. Asks what it cannot see and never records secret values.

SkillDevOpsv0.1.1 (latest)

Use in Claude Save Like Clone Comment

Activity: New: be the first to try it
Installs: 0 installs
Likes: 0 likes
Clones: 0 clones

Compare 0.1.0 with 0.1.1

0.1.1
7 Nov 2026
Scan passedNo tests
0.1.0
7 Nov 2026
Scan passedNo tests

Use in Claude

Ask Claude, with the connector

Install @slashclone/deploy-guide from SlashClone

Claude Code, with the plugin

/kit add @slashclone/deploy-guide

CLI

slashclone add @slashclone/deploy-guide

Codex

slashclone add @slashclone/deploy-guide --agent codex

Not enforced. Codex does not enforce the permissions this kit declares.

Cursor

slashclone add @slashclone/deploy-guide --agent cursor

Not enforced. Cursor does not enforce the permissions this kit declares.

claude.ai and the desktop app

Download for Claude

Not enforced. claude.ai and the Claude desktop app do not enforce the permissions this kit declares. How to upload it

As a file

Download .kit

One file with everything in it. slashclone add ./file.kit checks it against this page before installing.

Review before installing

Set up SlashClone in Claude

Health

No keep-alive checks yet

Checks run weekly once someone keeps the kit installed.

Run reports are off

Safety

Scan passed
Not reviewed yet
No tests

This kit reads docs/**, README.md, .github/**, **/package.json, .env.example, **/.env.example, **/Dockerfile, **/*.toml, **/*.yml, **/*.yaml, *.json, **/*.ts, **/*.tsx, **/*.js, **/*.mjs, **/*.py, writes to docs/DEPLOY.md and runs git log, git rev-parse. Install it?

Full scan and review

Similar kits

Stop bugs that only happen in production
@slashclone
A CLAUDE.md rule that stops bugs that only show up in production by keeping development and production behaving the same. Your agent prefers explicit env flags over NODE_ENV checks and records every unavoidable difference in your deploy guide, in the same change that adds it. Shows you the edit before saving.
Safe automatic deploys from GitHub Actions
@slashclone
Deploy to production only when tests pass, automatically or with one button, and always know what is live. A GitHub Actions release that ships main's head or stops and says why, records each release as a GitHub deployment, smoke tests, and rolls back on failure. Writes the workflow for you to review; never deploys or stores secrets itself.
Fix a failed Vercel or Netlify deploy
@shipcheck
Fix a deploy that works locally but fails on Vercel or Netlify: paste the build log, get the likely cause and the fix. Finds the first real error and matches about twenty common failures, like letter-case imports, missing packages or env vars, window is not defined, lockfile drift, wrong Node version, and out of memory. Checks your code and asks before changing anything.
Check your site works after every deploy
@slashclone
Know a deploy worked before your users find out it did not: a short smoke test that checks your live site after each release. Checks the status endpoint, home page, search, sign-in redirects, and connected services, retrying while the deploy settles, and exits non-zero so the release can roll back. Read-only, no credentials.

Link

https://slashclone.dev/@slashclone/deploy-guide

README badge

[![Install with SlashClone](https://slashclone.dev/badge/slashclone/deploy-guide.svg)](https://slashclone.dev/@slashclone/deploy-guide?ref=slashclone)

Embed

<iframe src="https://slashclone.dev/embed/slashclone/deploy-guide" width="480" height="200" title="@slashclone/deploy-guide" loading="lazy"></iframe>

Share card image

More from @slashclone

A session log that parallel agents never conflict on
Keep a project log that several Claude Code sessions can write at once without merge conflicts. Each session writes its own dated file, an index is generated instead of hand edited, and a small CI check makes sure every entry carries the line your team requires. Writes the files for you to review; never commits or pushes.
Parallel sessions
Build faster with several Claude Code sessions at once. Splits a big plan into independent workstreams, writes a brief for each, runs each in its own git worktree and branch, and merges every pull request on green CI in a safe order. Works in the Claude Code desktop app and in the terminal.
Embed YouTube videos without tracking cookies
Embed YouTube videos on your site without loading anything from Google until the visitor presses Play or allows videos. A click-to-play placeholder with a local poster swaps in the youtube-nocookie.com player, with a keyboard-friendly button, no layout shift, CSP entries, and a Playwright test that proves no YouTube request happens first. React and HTML templates. Not legal advice.
Decide what to measure and build a metrics dashboard
Figure out what to measure in your web app and build a staff-only metrics dashboard for activation, retention, and funnels. You pick a few numbers per stage, write how each is counted, and compute most from tables you already have, so user data stays on your servers. Adds an audit log with no user content and loads any browser analytics only after consent.

See all of @slashclone's kits

Report this kit