testing-quality

Audit test suites and categorize tests as RED, YELLOW, or GREEN.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/joshsymonds/gambit --skill testing-quality-joshsymonds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-quality
Source: https://github.com/joshsymonds/gambit/tree/main/skills/testing-quality
Command: npx skills add https://github.com/joshsymonds/gambit --skill testing-quality-joshsymonds

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill identifies and helps you eliminate ineffective tests that provide false confidence, ensuring your test suite actually catches bugs and doesn't just inflate coverage metrics.

Core Features & Use Cases

  • Test Auditing: Critically analyzes tests to categorize them as RED (remove/replace), YELLOW (strengthen), or GREEN (effective).
  • Bug Pattern Identification: Detects common anti-patterns like tautological tests, mock-testing, and weak assertions.
  • Corner Case Discovery: Identifies missing edge-case tests crucial for robust software.
  • Use Case: You have 95% test coverage but still encounter production bugs. Use this Skill to audit your test suite, find the "coverage gaming" tests, and create actionable tasks to improve the quality and effectiveness of your testing.

Quick Start

Use the testing-quality skill to audit the tests in the 'auth' module.

Frequently Asked Questions about testing-quality

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

FAQPage Schema
Why do I still find production bugs with 95% test coverage?

High test coverage can hide ineffective tests that inflate metrics without catching bugs. A test audit identifies tautological tests, weak assertions, and coverage gaming, replacing them with effective tests that verify actual software behavior.

How do I audit my test suite for genuine effectiveness?

To audit test suite effectiveness, categorize tests as RED (remove/replace), YELLOW (strengthen), or GREEN (effective). This process detects anti-patterns like mock-overuse and weak assertions, generating actionable tasks to improve bug detection.

What are common test anti-patterns that inflate coverage metrics?

Common test anti-patterns include tautological tests that prove nothing, excessive mocking, and weak assertions that fail to validate corner cases. These patterns create false confidence by gaming coverage metrics instead of catching actual bugs.

Can I audit tests for a specific module like authentication?

Yes, you can audit tests for a specific module like auth. The audit applies SRE-level scrutiny to that module's test suite, identifying missing corner cases and generating actionable improvement tasks targeted to that codebase area.

What is the difference between RED and YELLOW tests in a code audit?

In a test audit, RED tests are completely ineffective and should be removed or replaced, while YELLOW tests have some value but require strengthening through better assertions or broader corner case coverage to be effective.