Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@slashclone

Production smoke test

@slashclone/production-smoke-test

Write a short smoke test script for a live site: the status endpoint, the home page, search, sign-in redirects, and any connected services, each retried while a new deploy settles. Exits non-zero on the first failure so a release can roll back.

SkillDevOpsv0.1.0 (latest)
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it

How this works

  1. It is a skill: written instructions Claude reads when your request matches what the skill is for. You do not call it by name; just ask for the task.
  2. While it works, it reads and changes files in the places it lists, nowhere else.
  3. Nothing runs until you choose to use it, and you can remove it any time.

SKILL.md

Production smoke test

A smoke test answers one question after a deploy: is the site up and doing its main jobs? It is not a test suite. Five to ten checks, under three minutes, read-only.

What to check

Pick the checks that match the app. Good defaults:

  1. Status endpoint: returns OK and reports each dependency (database, storage, other services) as up. Add one if the app has none.
  2. Home page: HTTP 200.
  3. The main read path: a search or list endpoint returns at least one result for a query that always has results.
  4. Sign-in: each provider's start URL redirects to the provider with the production callback URL (catches a wrong base URL or missing env var). Never sign in.
  5. Connected services: each health endpoint answers, and protected endpoints refuse a request with no credentials (401), so auth was not switched off.

How to write it

  • Bash with set -uo pipefail, curl with --max-time, and a retry helper that tries each check for about two minutes while a new deploy settles.
  • Base URLs from environment variables with production defaults, so it can run against staging too.
  • Print ok: name or FAILED: name per check, run them all, and exit non-zero if any failed.
  • No credentials, no writes, no personal data in requests.

After writing

Run it once against production and show the output. Then wire it into the release workflow after the deploy step, with rollback on failure.

Files

  • SKILL.md
  • kit.json

Did it work?

0worked for them0did not work

Sign in to say whether it worked for you.

Nobody has said yet. Tried it? Tell the next person.