wa:validate-quality

Run tests, linting, formatting, and type checks with rigor-based gate selection.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-validate-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:validate-quality
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/validate-quality
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-validate-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably validate code quality by running the right combination of quality gates (tests, linting, formatting checks, and type checking) based on the current development rigor.

Core Features & Use Cases

  • Mode-calibrated gate selection: Automatically chooses which gates to run for lite, standard, or strict rigor, and supports overriding with a flag.
  • Tooling detection from project config: Determines available test runner, linter, formatter, and type checker by inspecting common config files.
  • Full reporting and verdict enforcement: Captures results for each executed gate, reports all failures, and computes an overall pass/fail outcome using a required quality-gate verdict step.

Quick Start

Run quality gates with increased confidence using: /validate-quality --rigor strict

Frequently Asked Questions about wa:validate-quality

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

FAQPage Schema
How do I run tests, linting, and type checking automatically in my CI workflow?

You can automate quality validation by running tests, linting, formatting checks, and type checking under a rigor-calibrated plan. The process detects tooling from project configuration and computes a pass/fail verdict across all executed gates.

What's the best way to enforce quality gates based on project rigor?

Enforcing quality gates is handled through mode-calibrated selection, automatically choosing which tests, linters, and type checks to run for lite, standard, or strict rigor levels. You can override the automatic selection using a flag.

How does tool detection work for test runners and linters?

Tool detection works by inspecting common project configuration files to determine the available test runner, linter, formatter, and type checker. This allows the validation process to execute the correct tools without manual specification.

Can I override which quality checks run during the validation process?

Yes, you can override the automatically selected quality checks by passing a rigor flag. This allows you to manually enforce a strict, standard, or lite validation plan regardless of the detected development rigor.

How are validation failures reported when a quality gate fails?

Validation failures are reported through independent gate result capture, which provides a comprehensive failure listing for each executed gate. A final validation verdict is computed across all gates to determine the overall pass or fail outcome.