coverage-run

Collect and aggregate Vitest, Playwright, and pytest coverage into unified snapshots.

1|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill coverage-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverage-run
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/coverage-run
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill coverage-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the collection, parsing, and snapshotting of test coverage results so teams can measure and track coverage across multiple local test stacks without manual aggregation.

Core Features & Use Cases

  • Multi-stack aggregation: Run Vitest, Playwright, and pytest coverage sequentially or scoped to specific packages and combine results into a unified snapshot.
  • Scoped and filtered runs: Support for Turborepo passthrough flags and package filtering to exclude broken test packages or target only specific services.
  • Snapshot history and reporting: Parse JSON summaries, count E2E specs for route coverage, and append standardized snapshots to a .coverage-history file for longitudinal tracking.
  • Use Case: CI troubleshooting where a developer needs a single coverage summary across JS unit tests, browser E2E route counts, and Python service coverage.

Quick Start

Run the coverage-run skill to collect Vitest, Playwright, and pytest coverage and append a unified snapshot to .coverage-history/snapshots.jsonl.

Frequently Asked Questions about coverage-run

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

FAQPage Schema
How do I aggregate test coverage across Vitest, Playwright, and pytest in a monorepo?

Aggregate test coverage across Vitest, Playwright, and pytest by running the stacks sequentially or scoped to specific packages, then parsing JSON summaries and counting E2E specs into a unified snapshot appended to .coverage-history/snapshots.jsonl.

Can I scope test coverage runs to specific packages using Turborepo passthrough flags?

Yes, you can scope test coverage runs using Turborepo passthrough flags and package filtering to target specific services or exclude broken test packages from the unified snapshot.

What is the best way to track test coverage history longitudinally across multiple stacks?

Track test coverage history by appending standardized snapshots combining JS unit tests, browser E2E route counts, and Python service coverage to a .coverage-history/snapshots.jsonl file for longitudinal tracking.

Does coverage-run activate the Python virtual environment automatically for pytest?

Yes, the coverage-run process activates Python virtual environments automatically before executing pytest services to ensure accurate coverage collection and parsing.

How do I exclude broken test packages from a monorepo coverage report?

Exclude broken test packages from a monorepo coverage report by applying package filtering and Turborepo passthrough flags to scope the run, preventing broken packages from polluting the unified snapshot.