Run Testing Suite

Run repository test commands with preflight checks and pass/fail reports.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill run-testing-suite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Run Testing Suite
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/run-testing-suite
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill run-testing-suite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool provides safe, deterministic repo validation to prevent production risks during validation.

Core Features & Use Cases

  • Discover and run repository-specific test commands in a safe order (lint, type checks, unit tests) with production-blocking preflight checks.
  • Enforce environment gating (APP_ENV=ci) and report clear pass/fail results with root-cause summaries.
  • Use case: Before merging, validate a multi-repo change set to ensure tests pass across services and detect regressions early.

Quick Start

Run the testing suite on your repository to perform preflight checks and generate a pass/fail report.

Frequently Asked Questions about Run Testing Suite

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

FAQPage Schema
How do I automate repo validation and run tests safely before merging?

Automate repo validation by running safe, production-blocking preflight checks before executing tests. This ensures deterministic test execution across multiple repos to detect regressions early before merging changes.

What is the best way to validate a multi-repo change set for regressions?

Validate a multi-repo change set by discovering repository-specific test commands and executing them in a safe order. This applies sequential gate execution to ensure tests pass across services and detect regressions early.

How do preflight safety gates prevent production risks during test execution?

Preflight safety gates prevent production risks by enforcing environment gating with APP_ENV=ci. This ensures validation runs deterministically in a safe state, blocking unsafe operations before test commands execute.

Does repo validation work without setting the CI environment variable?

Repo validation requires the APP_ENV=ci environment variable to enforce environment gating. This safety gate ensures deterministic execution and prevents production risks by strictly validating the runtime context before running tests.

What is included in the pass/fail report after running a testing suite?

The pass/fail report provides clear results with root-cause summaries after running the testing suite. It applies sequential gate execution for lint, type checks, and unit tests to give a deterministic validation outcome.

Why does test execution fail the validation gate in a multi-repo setup?

Test execution fails the validation gate if repository-specific commands for lint, type checks, or unit tests do not pass sequentially. The suite reports a clear root-cause summary to identify which safety gate blocked the process.