test-quiet

Hide passing vitest output and surface failures with jq and bunx.

6|3|Updated Jan 28, 2026

Search Tags:#automation #vitest #debugging #test #output #ci

Ready to run

npx skills add https://github.com/jamesaphoenix/tx --skill test-quiet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-quiet
Source: https://github.com/jamesaphoenix/tx/tree/main/.claude/skills/test-quiet
Command: npx skills add https://github.com/jamesaphoenix/tx --skill test-quiet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, bunx, vitest, and includes scripts (resource) components.

What problem does it solve?

Running large test suites often yields overwhelming output from passing tests. This Skill reduces noise by hiding passing test output and surfacing only failures, enabling faster debugging.

Core Features & Use Cases

Hides passing test output and shows failures with test name and first error line.
Detects flaky tests by re-running failing tests a configurable number of times.
Integrates with vitest and Bun-based runners to provide concise, deterministic feedback in CI and local development.

Quick Start

Run the script to execute tests with context-efficient output and visible failures.

Frequently Asked Questions about test-quiet

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

FAQPage Schema

How do I hide passing test output in vitest and only show failures?▼

Hiding passing vitest output requires parsing the test results as JSON and filtering for failures. This Skill uses a Bash runner with jq to parse vitest JSON output from bunx, surfacing only the failing test name and its first error line to reduce noise in large test suites.

Can I detect flaky tests in my CI workflow with vitest?▼

Detecting flaky tests in CI involves re-running failing vitest tests a configurable number of times. This Skill provides optional flags to automate flaky test detection, invoking the runner repeatedly to surface inconsistent failures and provide fast, actionable feedback.

Do I need jq and bunx installed to run vitest test automation scripts?▼

Yes, you need jq and bunx installed to run this test automation. The Bash-based runner relies on jq for parsing vitest JSON output and uses bunx to execute the vitest test runner, making both dependencies essential for processing and surfacing test failures.

What is the best way to reduce test output noise for large test suites?▼

The best way to reduce test output noise for large suites is hiding passing results and surfacing only failures. By parsing JSON output with jq and executing vitest through bunx, this approach ensures fast, actionable feedback on failures without overwhelming the console with passing test details.

Does this approach work for both local development and CI environments?▼

Yes, this approach works for both local development and CI environments. By hiding passing test output and surfacing only failures with concise error details, it provides deterministic, context-efficient feedback suitable for fast debugging locally and actionable reporting in CI workflows.