What problem does it solve? Teams often blur the line between quick post-deploy checks and full test suites, either overloading smoke tests until they lose their speed or skipping regression tests until old bugs resurface. This Skill defines the operational verification layer of testing—smoke, sanity, and regression tests—with explicit scope boundaries, step-by-step procedures, and completion checklists for each. ## Core Features & Use Cases - Smoke Testing: Defines a minimal gate that checks process health plus one critical path within seconds after a build or deploy, with binary pass/fail criteria wired into CI. - Sanity Testing: Verifies that a specific fix or small change behaves as intended, scoped narrowly to the changed code and its immediate neighbors. - Regression Testing: Establishes a workflow where every bug fix adds one reproduction test (tagged with its issue number), accumulated permanently and enforced in CI, including detection of skipped or silenced tests. - Use Case: After deploying a new build, run a two-assertion smoke suite to gate further testing; after fixing a full-width digit parsing bug, write a sanity test for that exact behavior; then add a regression test labeled with the bug number so the defect can never silently return. ## Quick Start Ask the AI to apply the levels-operational skill to design a smoke, sanity, or regression test suite for your current change or deployment.
