kova-testing

Select efficient verification workflows for Kova code changes using typecheck, lint, guard, or Vitest lanes.

Updated Aug 23, 2026

Search Tags:#vitest #testing strategy #release validation #change detection #kova #ci rerun #docker e2e

Ready to run

npx skills add https://github.com/chiragborse1/KovaLab --skill kova-testing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kova-testing
Source: https://github.com/chiragborse1/KovaLab/tree/main/.agents/skills/kova-testing
Command: npx skills add https://github.com/chiragborse1/KovaLab --skill kova-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasting time by helping you pick the smallest trustworthy test or CI path to validate a change and confidently debug failures.

Core Features & Use Cases

Change-scoped test selection: Determines whether to run typecheck/lint/guards only or Vitest targets based on what the diff touched, including cheap “changed” lanes.
Rerun-focused debugging: Guides you to reproduce narrowly first, inspect the exact failing job/SHA/artifacts, and rerun only the relevant lane or file.
Release-aware validation: Helps decide when to escalate from local proof to GitHub Actions and how to choose between narrower checks and full release validation.

Quick Start

Tell an AI agent: “Use kova-testing to choose the cheapest safe verification path for my current change, explain what to run, and then help me rerun only the relevant Kova lane if anything fails.”

Frequently Asked Questions about kova-testing

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

FAQPage Schema

How do I choose the cheapest safe Vitest lane to verify a code change?▼

To pick the cheapest safe Vitest lane, match the changed surface to the correct typecheck, lint, guard, or targeted Vitest targets. This workflow avoids unnecessary full suite execution by running only the minimum required validation.

How do I rerun only the responsible CI lane when debugging a failure?▼

To rerun only the responsible CI lane, reproduce the failure narrowly first, inspect the exact failing job, SHA, and artifacts, then trigger only the relevant E2E lane or file. This avoids rerunning the entire pipeline unnecessarily.

When should I escalate local test validation to GitHub Actions for a release?▼

You should escalate local test validation to GitHub Actions for a release when local proof is insufficient for release-aware validation. Escalate from narrower checks to full release validation to ensure comprehensive coverage before deployment.

Do I need Docker to run E2E tests for every change detection check?▼

No, you do not need Docker for every change detection check. You can avoid expensive Docker or full suite execution by selecting typecheck, lint, guard, or cheaper changed lanes based on what the diff actually touched.

What is the difference between check and test semantics in CI rerun strategies?▼

Check semantics validate code correctness via typecheck and lint, while test semantics validate behavior via Vitest and E2E lanes. Enforcing correct separation ensures you run the appropriate verification workflow without confusing the two processes.

Can I use kova-testing to validate releases without running the full test suite?▼

Yes, kova-testing helps validate releases by choosing between narrower checks and full release validation. It applies escalation rules using repository scripts and CI context to determine when narrower checks are sufficient for safe validation.