consolidate-test-suites

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.