smoke-and-sanity
Skill1 starsChanged 2 months agoMITView on GitHub
Build the 60-second smoke suite that decides whether a build is worth testing at all, plus the post-deploy sanity check that runs against production. Use after a deploy, when CI needs a fast first gate, or when asked "is the build alive".
In this repository34 other files it gives its agents.
- a11y-auditSkill
- api-contract-testingSkill
- autonomous-explorationSkill
- bug-reproSkill
- chaos-resilienceSkill
- ci-wiringSkill
- contract-testing-pactSkill
- coverage-ratchetSkill
- database-testingSkill
- e2e-authoringSkill
- environment-paritySkill
- exploratory-chartersSkill
- false-positive-hunterSkill
- flake-forensicsSkill
- i18n-l10n-testingSkill
- load-and-stressSkill
- mutation-proofSkill
- never-break-prodSkill
- payment-testingSkill
- perf-budgetSkill
- qa-triageSkill
- regression-curationSkill
- release-gateSkill
- responsive-mobile-testingSkill
- risk-mapSkill
- root-cause-protocolSkill
- security-regressionSkill
- state-machine-testingSkill
- test-data-managementSkill
- test-strategySkill
- tracking-testingSkill
- transactional-email-testingSkill
- unit-test-authoringSkill
- visual-regressionSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
No uncaught JS exception and no 5xx on load.
- Distinctive: line 21
If a check needs setup that can fail for its own reasons, it does not belong in smoke.
- Distinctive: line 37
Never grow smoke into a regression suite.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Smoke & Sanity
Smoke answers one question: is this build worth anyone's time? It runs in under a minute, it never flakes, and if it is red nothing else runs.
The smoke set (5-10 checks, no more)
- The app responds — expected status, not a 500 or a maintenance page.
- The root document renders real content, not an empty shell.
- Auth works: one seeded user can log in and reach a private route.
- The primary read path returns data (list loads with at least one row).
- The primary write path accepts one write and reflects it.
- No uncaught JS exception and no 5xx on load.
- The version/build id served matches the version just deployed.
If a check needs setup that can fail for its own reasons, it does not belong in smoke.
node runner/bin/qa-supreme.mjs smoke --url https://staging.example.comSanity after deploy (production-safe)
Same shape, read-only, no data written, no destructive verbs. Run it within 60 seconds of every promotion, and again 5 minutes later — the second run catches cache and CDN issues the first cannot see.
Rules
- Smoke is a gate, not a report. Its only outputs are GO and NO-GO with the failing check named.
- A flaky smoke test is an emergency: it destroys the meaning of the gate. Fix or delete it same day.
- Never grow smoke into a regression suite. When it passes 90 seconds, split it.
- Version assertion is not optional: half of "the fix didn't work" incidents are "the fix wasn't deployed".
Output
SMOKE https://staging.example.com build 4f2a91c
reachable PASS HTTP 200 in 240ms
auth round-trip PASS seeded user reached /dashboard
primary read PASS 12 rows
version matches deploy FAIL served 4f2a91c, expected 8b1d07e
VERDICT: NO-GO — the deploy did not reach the served buildDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

