AGENT SKILL

smoke-test

Run the smoke checks a repository declares for its deploy targets and report whether production actually answers after a release. Use after a deploy, during release verification, and when confirming a rollback landed. Triggers on: "smoke test", "run smoke checks", "is production healthy", "did the deploy work", "verify the release is live".

使用场景测试与质量
License 许可
MIT
最近更新
2026-10-26
Stars
★ 0
Forks
0

01 前言 Front Matter

id
smoke-test
name
smoke-test
task
[ "diagnostics", "runtime-ops" ]
type
skill
model
sonnet
owner
@kaiohenricunha
tools
Bash, Read, Grep, Glob
domain
[ "infra", "devex" ]
effort
medium
created
1789689600000
updated
1789689600000
version
1.0.0
dotbabel
{ "compute": { "mode": "dynamic", "binding": "consumer", "requirement": "routine" } }
maturity
draft
platform
[ "vercel", "flyio", "aws" ]
description
Run the smoke checks a repository declares for its deploy targets and report whether production actually answers after a release. Use after a deploy, during release verification, and when confirming a rollback landed. Triggers on: "smoke test", "run smoke checks", "is production healthy", "did the deploy work", "verify the release is live".
allowed-tools
Read Grep Glob Bash
argument-hint
[--dry-run] [--json]
user-invocable
true
disable-model-invocation
true

03 SKILL.md 正文

Smoke Test

Run the smoke checks declared per target in .claude/deploy-targets.json and report whether the deployed thing actually answers.

disable-model-invocation: true is deliberate. These checks execute commands the repository declares and send requests to production, so this skill runs when a person asks for it, not when a model infers it might be useful.

Workflow

  1. Resolve the helper script — the same two-step resolution deploy-status uses, because it is the same helper and a skill that found only one of the two locations would work for exactly one install shape:

    if [ -f "$HOME/.claude/skills/deploy-status/scripts/deploy-ops.mjs" ]; then
      DEPLOY_OPS="$HOME/.claude/skills/deploy-status/scripts/deploy-ops.mjs"
    elif [ -f "skills/deploy-status/scripts/deploy-ops.mjs" ]; then
      DEPLOY_OPS="skills/deploy-status/scripts/deploy-ops.mjs"
    else
      echo "deploy-status helper not found; re-run dotbabel bootstrap or dotbabel init" >&2
      exit 2
    fi
    
  2. Run the smoke command from the consuming project root, forwarding only the flags this skill documents:

    node "$DEPLOY_OPS" smoke $ARGUMENTS
    

    $ARGUMENTS is raw caller text spliced into a command that reaches production, so pass only --dry-run and --json — drop anything else rather than forwarding it. A value carrying ;, |, &, a backtick, $(, or a newline is shell syntax, not a flag: refuse it and say so.

  3. Preserve the helper's exit code:

    • 0 — every declared check passed, or none is declared, or it was a dry run. None of those is a failure.
    • 1 — at least one check failed, or the run hit its 300-second budget.
    • 2 — target discovery failed.
  4. Read verdict, not just the exit code. The payload distinguishes four states, and two of them exit 0 without having verified anything:

    verdict Meaning
    pass Every declared check ran and passed
    fail At least one check failed, or the budget was hit
    not_configured No target declares smoke — nothing was checked
    not_run --dry-run; checks were listed, none executed

    Report not_configured and not_run as exactly that. Reporting either as a pass claims a verification that did not happen.

On failure

Report the failing checks and recommend /rollback-prod. Then stop.

Never invoke /rollback-prod, and never run the rollback helper directly. Rolling back is a production change, and both the rule floor and KD-13 require an explicit human instruction for one. /rollback-prod additionally demands a typed confirmation of its own, which exists precisely so that a chain of automated judgments cannot end in an unattended production change.

Recommend it, name the failing checks, and let the person decide.

What the checks are

Declared per target in .claude/deploy-targets.json; see skills/deploy-status/SKILL.md for the full schema and the security guards. In short: http checks are GET only, retry 3 times with 2s/4s/8s backoff, and abort after 10 seconds; command checks run their argv exactly once, because a command may not be idempotent.

Secrets are read only from named environment variables, and header values never appear in the output. If a check needs a token, export it before invoking:

SMOKE_BEARER=… /smoke-test

Rules

  • Never roll back. Recommend /rollback-prod and stop.
  • Never deploy or promote. This skill only observes.
  • Never invent a smoke check. If a target declares none, report not_configured rather than guessing at a health endpoint.
  • Never report a dry run as a pass. --dry-run lists what would run and verifies nothing; its verdict is not_run.
  • Never print a header value. The helper redacts them; do not echo the environment variable it read them from either.

04 同仓库更多 Skills

kaiohenricunha
kaiohenricunha/dotbabel

yolo

Start temporary autonomy for the current task or an explicit scope with a required --for expiry. Codex permits scoped pushes, merges, deploys, and releases after strict testing and validation; Full access is a separate runtime setting. Claude Code uses a session permission hook with a protected-action denylist.

开发工程师
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

veracity-audit

Audit a data pipeline for Veracity and Value. Dispatches data-scientist, compliance-auditor, and data-engineer agents with project context injected at dispatch time. All source paths are supplied via flags — no defaults, no project assumptions. Subcommands: audit (full pipeline walk), score-check (scoring math only), gate-check (gate coverage only), source-trace <label> (single source end-to-end). Invoke when: "audit pipeline", "veracity check", "scoring math correct?", "check gates", "trace source", "verify quality gates", "formula correct?".

律师与法务Skill与智能体开发
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

validate-spec

Audit an already-implemented spec against the codebase. Walks each constraint (ARCH-N, PERF-N, KD-N, etc.) and acceptance criterion, grounds findings in file:line evidence, runs the spec.json acceptance_commands, and writes a single audit doc to docs/audits/. Use whenever the user asks to "validate a spec", "audit a spec", "check if spec is implemented", "verify the spec is done", "is this spec really done", or otherwise wants closure on spec-driven work. Read-only against the spec — produces an audit, never modifies the spec itself.

★ 0
kaiohenricunha
kaiohenricunha/dotbabel

terragrunt-specialist

Deep-dive Terragrunt hierarchy review, DRY pattern audits, and run-all orchestration analysis. Use for structured investigations of multi-environment Terragrunt layouts, dependency graphs, remote state config, and hook correctness. Triggers on: "Terragrunt audit", "run-all review", "dependency block", "DRY pattern review", "env hierarchy audit", "mock_outputs", "terragrunt hooks".

运维与部署
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

terraform-specialist

Deep-dive Terraform architecture review, module design, state management, and migration. Use for structured investigations of Terraform workspaces, provider configuration, module coupling, import workflows, and test coverage. Triggers on: "Terraform audit", "module review", "state management", "Terraform import", "workspace design", "provider config review", "Terraform testing".

测试与质量运维与部署
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

spec

Create structured engineering specs through interactive pairing. Use when the user wants to create a spec, design doc, technical specification, architecture document, RFC, or engineering plan. Triggers on "let's spec this out", "create a spec", "design doc", "write a technical plan", "plan the architecture". Works for greenfield and brownfield projects. Outputs to docs/specs/.

设计师视觉设计
★ 0