accelint-ts-testing

Audit Vitest test suites and produce improvement recommendations.

21|4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/gohypergiant/agent-skills --skill accelint-ts-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accelint-ts-testing
Source: https://github.com/gohypergiant/agent-skills/tree/main/skills/accelint-ts-testing
Command: npx skills add https://github.com/gohypergiant/agent-skills --skill accelint-ts-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework to audit and improve Vitest test suites, guiding teams to adopt consistent patterns, reduce flaky tests, and raise overall test quality.

Core Features & Use Cases

  • Pattern guidance for organizing tests (AAA, describe structure, parameterized tests) and selecting appropriate test doubles.
  • Quality references linking to curated rules in references/ (e.g., AAA pattern, assertions, async testing, mocks).
  • Config guidance on global mock cleanup and setup to ensure test isolation across the project.
  • Review workflow to produce actionable feedback and improvement suggestions for test files.

Quick Start

Use accelint-ts-testing to inspect vitest test suites and produce improvement recommendations for test organization, assertions, mocks, and performance.

Frequently Asked Questions about accelint-ts-testing

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

FAQPage Schema
How do I audit vitest tests to fix over-mocking and loose assertions?

To audit vitest tests, inspect *.test.ts or *.spec.ts files for over-mocking and loose assertions, then apply structured refactoring patterns like AAA and it.each to ensure reliable, maintainable test suites.

What is the AAA pattern for organizing vitest unit tests?

The AAA pattern for vitest unit tests structures test logic into Arrange, Act, and Assert phases, reducing flaky tests by enforcing clear separation of setup, execution, and verification within nested describe blocks.

How do I structure vitest describe blocks and parameterized tests?

Structure vitest describe blocks by grouping related tests logically, and use it.each for parameterized tests to drive structured refactoring, ensuring consistent patterns and improving overall test suite maintainability.

How do I fix slow vitest tests and ensure proper test isolation?

Fix slow vitest tests and ensure test isolation by applying global config guidance for mock cleanup, reviewing async testing patterns, and enforcing structured refactoring to eliminate flaky test scenarios.

Does this vitest testing approach work with existing test files?

Yes, the vitest testing approach reviews existing *.test.ts or *.spec.ts files, identifying nested describe blocks and over-mocking to produce actionable feedback and improvement suggestions for test files.

Why do my vitest mocks cause flaky tests across the project?

Vitest mocks cause flaky tests when global mock cleanup is not configured properly, making test isolation fail; applying global config guidance for setup and cleanup ensures reliable, maintainable test suites.