test-analyzer

Parse Vitest JSON output to generate test quality metrics and reports.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/cffrank/paperclip-skills-agents --skill test-analyzer-cffrank
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-analyzer
Source: https://github.com/cffrank/paperclip-skills-agents/tree/main/skills/test-analyzer
Command: npx skills add https://github.com/cffrank/paperclip-skills-agents --skill test-analyzer-cffrank

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test results analysis, quality metrics, flaky test detection, and coverage trend tracking for Vitest suites running in the workerd runtime. Transforms raw test output into actionable insights — pass rates, slowest tests, coverage diffs, and sprint quality reports. Use when analyzing test failures, identifying flaky tests, generating quality reports, tracking coverage trends, or diagnosing slow test suites. Triggers on: "test results", "flaky test", "test analysis", "quality report", "coverage trend", "slow tests", "test metrics", "sprint quality", "test health", "why did tests fail", "test dashboard", or any request to interpret or summarize test output.

Core Features & Use Cases

  • Parse structured Vitest JSON output to transform test results into usable quality metrics.
  • Identify flaky tests and provide quarantine/trends analysis to improve stability.
  • Track coverage trends, slow tests, and generate sprint-quality reports for leadership and CI dashboards.
  • Provide actionable recommendations and diagnostics to speed up debugging after failures.

Quick Start

Provide Vitest JSON output from your CI and run the skill to generate a sprint quality report.

Frequently Asked Questions about test-analyzer

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

FAQPage Schema
How do I analyze Vitest JSON output to identify flaky tests and coverage trends?

Vitest JSON output analysis parses structured test results to identify flaky tests, track coverage trends, and generate sprint quality reports. It transforms raw test data into actionable quality metrics like pass rates and slowest tests.

What is the best way to generate a sprint quality report from CI test runs?

Sprint quality reports are generated by applying test analysis across CI runs. It aggregates pass rates, failure diagnostics, and coverage diffs from Vitest JSON output to yield a comprehensive sprint-quality view for leadership dashboards.

Can I use this test analysis approach for Vitest suites running in the workerd runtime?

Test analysis for Vitest suites running in the workerd runtime is fully supported. It processes structured JSON output from this environment to detect performance bottlenecks, track coverage changes, and identify flaky tests.

How do I diagnose slow tests and performance bottlenecks in my test suite?

Diagnosing slow tests involves parsing Vitest JSON output to isolate performance bottlenecks within your test suites. It identifies the slowest tests and provides actionable diagnostics to speed up debugging after failures.

Why did my tests fail and how can I get actionable recommendations for debugging?

Test failures are analyzed by parsing structured Vitest JSON output to pinpoint exact failure points. It provides actionable recommendations and diagnostics from the test results to speed up debugging after failures.

What limitations exist when tracking coverage trends from raw Vitest output?

Tracking coverage trends requires structured Vitest JSON output rather than raw console logs. Without structured input, generating coverage diffs, identifying flaky tests, and yielding sprint quality views is not possible.