consolidate-test-suites

Assign each AGH test change to one owning layer by invariant.

182|8|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/compozy/agh --skill consolidate-test-suites
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consolidate-test-suites
Source: https://github.com/compozy/agh/tree/main/.agents/skills/consolidate-test-suites
Command: npx skills add https://github.com/compozy/agh --skill consolidate-test-suites

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents low-signal, misplaced, or redundant tests by forcing a clear decision about the invariant being protected and the canonical test suite responsible for proving it.

Core Features & Use Cases

  • Invariant-first test decisions: Defines what must remain true before changing or adding coverage, with an explicit stop condition when no durable behavior or boundary can be named.
  • Owning-layer placement: Selects exactly one primary owning layer (e.g., unit, integration, end-to-end, static analysis) so the right suite proves the right failure mode.
  • Canonical suite reuse: Recommends reusing and updating existing canonical test suites and only creating standalone regression tests when allowed, with documented rationale.
  • Low-signal test rejection: Discourages brittle tests that freeze implementation details, prose/snapshot literals, config shape, or file-existence checks without contract value.
  • Decision recording: Ensures outcomes include the invariant, owning layer, what changed (or why nothing was added), and the verification command.

Quick Start

Use this skill when planning a test change in AGH to determine the invariant, choose the owning layer, and locate or update the canonical suite before writing or moving any tests.

Frequently Asked Questions about consolidate-test-suites

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

FAQPage Schema
How do I decide which test layer should own a new regression test?

To decide the owning layer for a regression test, first identify the specific invariant being protected, then select exactly one primary layer such as unit, integration, or end-to-end to prove that exact failure mode.

What is invariant-first testing and when should I use it?

Invariant-first testing defines what durable behavior or boundary must remain true before changing coverage, requiring an explicit stop condition when no durable public contract can be named for the test.

How do I avoid writing low-signal tests that lock in implementation details?

Avoid low-signal tests by rejecting brittle coverage that freezes implementation details, prose literals, config shapes, or file-existence checks, and instead prove durable public contracts through canonical suites.

When should I create a standalone regression test instead of updating an existing suite?

Create a standalone regression test only as a fallback when canonical suites cannot cover the invariant, documenting the rationale, while prioritizing the reuse and update of existing canonical test suites.

What should be recorded when consolidating test coverage decisions across unit and end-to-end suites?

Record the invariant, the assigned owning layer, what changed or why nothing was added, and the verification command to ensure clear ownership and prevent redundant or misplaced tests.