qa-smoke-test

Execute a predefined checklist to validate backend, frontend, safety, and delivery.

Updated May 15, 2026
One-click install
npx skills add https://github.com/ruskibeats/t1d --skill qa-smoke-test-ruskibeats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-smoke-test
Source: https://github.com/ruskibeats/t1d/tree/main/.pi/skills-archive/qa-smoke-test
Command: npx skills add https://github.com/ruskibeats/t1d --skill qa-smoke-test-ruskibeats

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a comprehensive checklist for validating the quality and integrity of the T1D Companion application, ensuring that all necessary checks are performed before delivery.

Core Features & Use Cases

  • Backend and Frontend Checks: Execute scripts to validate the application's backend and frontend functionality.
  • Safety Validation: Verify that the application behaves as expected in safety-critical scenarios.
  • Delivery Validation: Document the changes made and the checks run to ensure the application is ready for delivery.

Quick Start

Run the QA Smoke Test Skill to execute the checklist before delivering code changes.

Frequently Asked Questions about qa-smoke-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a smoke test for backend and frontend validation before deployment?

Run a predefined checklist using scripts and manual verification to validate backend and frontend functionality, ensuring all functional checks are completed before code delivery.

What is a QA smoke test checklist for application delivery?

A QA smoke test checklist validates backend, frontend, safety, and delivery readiness by executing scripts to verify functionality and documenting changes to ensure the application is ready for deployment.

How do I validate safety-critical scenarios in a companion application?

Validate safety-critical scenarios by executing a predefined checklist that verifies the application behaves as expected in safety situations, combining automated scripts with manual verification before delivery.

Can I use scripts to automate frontend and backend checks before code delivery?

Yes, you can execute scripts to validate both backend and frontend functionality, documenting the checks run and changes made to ensure the application is fully ready for delivery.

What steps are needed to ensure delivery validation for a T1D companion app?

Delivery validation requires running backend, frontend, and safety checks via scripts, then documenting the changes made and checks completed to confirm the application is ready for deployment.

Does smoke testing cover both functional and safety validation before deployment?

Yes, smoke testing covers both functional and safety validation by executing a predefined checklist that verifies backend, frontend, and safety-critical scenarios are completed prior to delivery.