plenum-validation-and-qa

Run pytest, Vitest, and Playwright suites while enforcing Plenum quality gates.

6|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/dhruvb14/smart-thermostat-with-vents --skill plenum-validation-and-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plenum-validation-and-qa
Source: https://github.com/dhruvb14/smart-thermostat-with-vents/tree/main/.claude/skills/plenum-validation-and-qa
Command: npx skills add https://github.com/dhruvb14/smart-thermostat-with-vents --skill plenum-validation-and-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers maintain reliable validation workflows for Plenum by explaining how to run tests, interpret failures, and satisfy repository quality gates without missing hidden contract requirements.

Core Features & Use Cases

  • Test Execution Guidance: Provides workflows for running backend pytest, frontend Vitest, and Playwright E2E suites with correct coverage handling.
  • Quality Gate Enforcement: Explains parity checks, API specification validation, addon configuration checks, coverage thresholds, and golden screenshot acceptance rules.
  • Use Case: When adding a Celsius temperature field or debugging a failing CI validation, use this Skill to identify required tests, fixtures, manifests, and evidence needed for acceptance.

Quick Start

Use the plenum-validation-and-qa skill to determine which tests and validation steps are required for my Plenum code change.

Frequently Asked Questions about plenum-validation-and-qa

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

FAQPage Schema
How do I fix failing quality gates in CI validation for pytest and Vitest?

Fix failing quality gates by identifying required tests, fixtures, and manifests, then resolving parity checks, API specification validation, and coverage thresholds to satisfy CI validation requirements.

What is the best way to enforce coverage thresholds across pytest, Vitest, and Playwright suites?

Enforce coverage thresholds by applying repository-specific testing patterns and acceptance rules, ensuring backend pytest, frontend Vitest, and Playwright E2E suites meet the required coverage handling parameters.

Why does my CI validation fail when adding a new temperature field to the HVAC control repository?

CI validation fails because adding fields requires satisfying cross-file contract maintenance, including parity checks, conversion safeguards, and addon configuration checks, alongside generating required test evidence.

How do I run Playwright E2E tests and handle golden screenshot acceptance rules?

Run Playwright E2E tests by following repository-specific workflows that validate golden screenshot acceptance rules, ensuring frontend changes meet visual regression thresholds and capture required evidence.

Do I need to maintain API specification parity checks for backend and frontend tests?

Yes, maintaining API specification parity checks is required to ensure backend pytest and frontend Vitest suites adhere to cross-file contract maintenance and pass CI validation quality gates.

When should I use cross-file contract maintenance for HVAC control repository testing?

Use cross-file contract maintenance when adding features or debugging CI validation failures, ensuring conversion safeguards, addon configuration checks, and acceptance thresholds are satisfied across test suites.