Skill guide

Test suite health

Assess the cost, stability, overlap, and maintainability of an existing test suite.

Use available timing, failure, retry, fixture, and configuration evidence to identify material suite problems. Recommendations distinguish measured behavior from static indicators and preserve tests that protect different failure modes.

Package version 0.1.0-beta.7

Included with Faye Coding Assistant

When to use

Use this when the deliverable is a suite-wide health assessment rather than the diagnosis of one failing test.

What to provide

  • The suite or package boundary and the concern to investigate.
  • Existing timing reports, CI history, retry records, fixtures, or other relevant evidence.

Expected results

  • Prioritized findings with measured or inferred evidence identified.
  • Bounded remediation or measurement recommendations and explicit evidence gaps.

Example requests

Try this request

Codex
Codex request
$test-suite-health Assess whether our browser suite has overlapping setup and unstable checks. Use the existing CI reports first and recommend changes without editing tests.
Grok
Grok request
/test-suite-health Assess whether our browser suite has overlapping setup and unstable checks. Use the existing CI reports first and recommend changes without editing tests.
Antigravity
Antigravity request
/test-suite-health Assess whether our browser suite has overlapping setup and unstable checks. Use the existing CI reports first and recommend changes without editing tests.

Requirements and limits

Before you start

  • Access to the suite and its available operational evidence.

Scope and limitations

  • Assessment does not edit, delete, or weaken tests.
  • A broad or costly suite is not run just to manufacture timing statistics.
  • Similar filenames or test size alone do not prove redundant coverage.
Technical source

The hosted file belongs to the package version shown on this page.

plugins/faye-coding-assistant/skills/test-suite-health

Open source file