test-all

Execute all tests across multi-package repositories and generate delta reports.

25|5|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Hedgehogues/awesome-claude --skill test-all-hedgehogues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-all
Source: https://github.com/Hedgehogues/awesome-claude/tree/main/skills/test-all
Command: npx skills add https://github.com/Hedgehogues/awesome-claude --skill test-all-hedgehogues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runs all tests across a multi-package repository, including integration and end-to-end tests, and provides a comprehensive report with deltas.

Core Features & Use Cases

  • Auto-discovers repository structure, test runners, and lint configurations to orchestrate tests across packages.
  • Executes unit, integration, end-to-end tests across all packages and reports full statistics with delta vs previous runs.
  • Supports scoped runs via arguments like skip-e2e or only-<package> to limit scope.

Quick Start

Run test-all to execute every test across your repository and generate a delta report.

Frequently Asked Questions about test-all

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

FAQPage Schema
How do I run all tests across a multi-package repository automatically?

To run all tests across a multi-package repository automatically, use a tool that auto-discovers your project layout and test runners to orchestrate unit, integration, and E2E tests deterministically. It then outputs a comprehensive delta report suitable for CI pipelines.

What is the best way to execute integration and E2E tests in a monorepo with diverse test runners?

Executing integration and E2E tests in a monorepo with diverse runners is best handled by an orchestration tool that detects your existing tooling and lint configurations. This approach runs tests deterministically across all packages and generates statistics with deltas from previous runs.

Can I skip end-to-end tests and run a specific package scope during CI?

Yes, you can skip E2E tests and limit scope to a specific package during CI by using scoped run arguments. Passing specific flags like skip-e2e or only-<package> restricts the test execution to the targeted package or test type.

How does test automation handle varying lint tools and project layouts in monorepos?

Test automation handles varying lint tools and project layouts in monorepos by auto-discovering the repository structure and configurations. It identifies the diverse test runners and lint tools present, enabling deterministic execution across the entire workspace without manual setup.

Does multi-package test automation provide delta reports for nightly runs?

Yes, multi-package test automation provides delta-rich reports for nightly runs. After executing all unit, integration, and end-to-end tests, it generates full statistics comparing the current results against previous runs to track regressions over time.

When should I use a unified test runner instead of executing package tests individually?

You should use a unified test runner instead of executing package tests individually when managing a monorepo with expensive integration and E2E tests. It enables selective scope by package or test type and provides a comprehensive delta report, which individual execution lacks.