smoke-test

Smoke Test

Trace a resource, event, or feature through the system and verify it works end-to-end.

Preferences

Read ~/.claude/skills/smoke-test/preferences.md using the Read tool. If not found, no preferences are set.

Project context

On startup, use Bash to detect: CLAUDE.md presence, project stack files (ls package.json Cargo.toml pyproject.toml go.mod requirements.txt), and current git branch. Skip any that fail.

Command routing

Check $ARGUMENTS:

• help → display help then stop
• config → interactive setup then stop
• reset → delete ~/.claude/skills/smoke-test/preferences.md, confirm, stop
• anything else → run smoke test

Help

Smoke Test — Trace and verify something works end-to-end

Usage:
  /smoke-test <natural language>       Build and run a trace plan
  /smoke-test config                   Set environment and verbosity defaults
  /smoke-test reset                    Clear preferences
  /smoke-test help                     This help

Examples:
  /smoke-test uploaded a file to workspace 30 in prod, check the pipeline
  /smoke-test verify login flow on staging
  /smoke-test did my migration run correctly in production?
  /smoke-test check webhook fires after order creation in dev

How it works:
  1. Reads project context (CLAUDE.md, repo structure, APIs)
  2. Builds a trace plan — ordered checks
  3. Confirms the plan with you
  4. Runs each check, reporting pass/fail
  5. Summarizes with diagnosis

Current preferences:
  (shown above under Preferences)

Config

Use AskUserQuestion:

Q1 — "Default environment?" (Production, Staging/Dev, Local, Ask each time (default)) Q2 — "Trace output verbosity?" (Concise, Detailed, Verbose on failure (default))

Save to ~/.claude/skills/smoke-test/preferences.md.

First-time detection

If no preferences file exists, show: "First time using /smoke-test? Run /smoke-test config to set default environment and verbosity, or continue — I'll auto-detect."