What problem does it solve?
This Skill eliminates the risk of teams mistaking pre-deploy static checks (like lint, unit tests, or exit code validation) for successful smoke testing, which often lets production bugs slip through because true smoke testing requires proving operator-visible outcomes work on the deployed surface with supporting ground-truth diagnostics.
Core Features & Use Cases
- Strict Smoke Contract Definition: Guides Product Owners to write smoke tests that require verifiable operator-visible outcomes and named ground-truth diagnostic surfaces, rather than relying on weak pre-deploy signals.
- End-to-End Smoke Execution: Provides AI Developers with a step-by-step process for running post-deploy smoke checks, including UI interaction testing, backend diagnostic cross-checking, adversarial falsification probes, and structured evidence collection.
- Use Case: When deploying a new client-facing help-desk feature, this Skill ensures the feature actually works for end users in production, rather than only passing pre-deploy automated checks that miss runtime or integration bugs.
Quick Start
Use the smoke-testing skill to define a post-deploy smoke test contract for your new feature and execute the required smoke checks after deployment to confirm operator-visible outcomes work correctly with supporting ground-truth diagnostics.
