aiactio-testing

Run Vitest validation covering lint, type-checking, tests, and build.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Hamza-037/AI-ACT --skill aiactio-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiactio-testing
Source: https://github.com/Hamza-037/AI-ACT/tree/main/skills/testing
Command: npx skills add https://github.com/Hamza-037/AI-ACT --skill aiactio-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The skill automates the complete Vitest validation workflow for aiactio projects, ensuring tests, linting, type checks, and builds pass before commits.

Core Features & Use Cases

  • Comprehensive testing conventions: mocks patterns for Supabase and Next/navigation, standard test patterns, and a complete verification script.
  • Enforces 0 skips, 0 todos, and passing tests before commit, supporting reliable code changes.
  • Use Case: when creating or updating features, run the full validation to guarantee test coverage and build integrity.

Quick Start

Run the complete validation script to lint, type-check, test, and build before committing.

Frequently Asked Questions about aiactio-testing

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

FAQPage Schema
How do I automate Vitest validation for lint, type-checking, and builds before committing?

Automating Vitest validation involves running a complete script that sequentially lints, type-checks, tests, and builds your project. This enforces 0 skips and 0 todos to guarantee code changes pass before committing.

How do I mock Supabase and Next/navigation in Vitest test suites?

Mocking Supabase and Next/navigation in Vitest requires applying standard project mock patterns. Using these patterns ensures isolated component testing and reliable validation during feature creation and updates.

Why does my Vitest suite fail before a commit despite passing locally?

Your Vitest suite may fail before a commit if it contains skipped tests or todos. Full validation enforces 0 skips, 0 todos, and passing tests to guarantee code integrity and satisfy project conventions.

What is the best way to enforce strict test quality and build integrity in a Vitest workflow?

Enforcing strict test quality in Vitest involves running a full validation script that checks lint, types, and builds. This enforces 0 skips and 0 todos, ensuring reliable code changes during feature updates.

Do I need specific beforeEach cleanup routines for Vitest validation?

Yes, Vitest validation requires standard beforeEach cleanup routines. These routines ensure state isolation between tests, which is necessary for accurate mock patterns and passing the full validation sequence.

Can I use this validation workflow for both feature creation and updates?

Yes, you can use this Vitest validation workflow for both feature creation and updates. It applies complete verification checks to guarantee test coverage and build integrity whenever you modify code.