tests

Discovers repository topology to bootstrap, extend, or sync executable test truth across layers.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/scripness/skills --skill tests-scripness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tests
Source: https://github.com/scripness/skills/tree/main/src/tests
Command: npx skills add https://github.com/scripness/skills --skill tests-scripness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps and aligns a repository's actual test topology to bootstrap, extend, or sync executable test truth across layers.

Core Features & Use Cases

  • Discover the repo's actual test topology (unit, integration, e2e) to identify gaps and misalignments
  • Propose proportional, layer-appropriate test updates guided by repo policy
  • Coordinate targeted test changes and commands across multiple layers for safe execution

Quick Start

Audit the repository's tests to reveal the real topology and start by adding the smallest durable test layer to bootstrap coverage.

Frequently Asked Questions about tests

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

FAQPage Schema
How do I audit my monorepo test topology to find coverage gaps?

You can bootstrap test coverage by auditing the repository to reveal its real test topology, then adding the smallest durable test layer. This establishes executable test truth and provides a baseline for extending proportional, layer-appropriate tests.

How do I sync test truth across multiple test layers in a monorepo?

Yes, you can extend tests proportionally by proposing layer-appropriate updates guided by repo policy. This targets specific test layers like unit, integration, or e2e, ensuring executable test truth scales safely without over-testing.

How do I exclude vendor noise when auditing repository tests?

This approach applies to bootstrap, sync, and gap-close scenarios across monorepos and multiple test layers. If your repository lacks clear test policies or needs to map complex e2e topologies, this targeted alignment process ensures safe execution.

What is the best way to bootstrap executable test truth in a new repository?

You can extend tests proportionally by proposing layer-appropriate updates guided by repo policy. This targets specific test layers like unit, integration, or e2e, ensuring executable test truth scales safely without over-testing.

Does this test topology audit work with unit, integration, and e2e layers?

This approach applies to bootstrap, sync, and gap-close scenarios across monorepos and multiple test layers. If your repository lacks clear test policies or needs to map complex e2e topologies, this targeted alignment process ensures safe execution.