Audit test suites to identify tautological tests, weak assertions, and missing corner cases.
npx skills add https://github.com/Veraticus/gambit --skill testing-quality
Please help me install this Agent Skill. Skill: testing-quality Source: https://github.com/Veraticus/gambit/tree/main/skills/testing-quality Command: npx skills add https://github.com/Veraticus/gambit --skill testing-quality
Audit test suites for real effectiveness, not vanity metrics. Identify tests that provide false confidence (tautological, mock-testing, line hitters) and missing corner cases. Create Tasks for improvements.
Core principle: Tests must catch bugs, not inflate coverage metrics.
CRITICAL MINDSET: Assume tests were written by junior engineers optimizing for coverage metrics. Default to skeptical—a test is RED or YELLOW until proven GREEN.
Announce at start: "I'm using gambit:testing-quality to audit these tests with SRE-level scrutiny."
Use gambit:testing-quality to initiate an audit of the current test suite and surface RED/YELLOW tests along with suggested improvements.
High-intent search queries and answers about installing and using this skill.
You can find tautological tests by auditing your suite to trace call paths against production code, identifying tests that assert on mocked values or lack real logic checks. This process categorizes tests into RED, YELLOW, and GREEN statuses based on actual bug-catching effectiveness.
A tautological test asserts its own mock setup rather than verifying production code, providing false confidence and inflating coverage metrics. Auditing identifies these weak assertions to ensure tests actually catch real bugs.
You audit tests for missing corner cases by reading production code first, systematically tracing test call paths to find gaps, and generating actionable tasks with concrete, testable success criteria to fill those coverage holes.
Yes, this audit approach applies across all codebases and test strategies, enforcing SRE-level scrutiny by defaulting to a skeptical mindset where tests are assumed RED or YELLOW until proven GREEN.
The best way to fix weak assertions is to follow a prioritized improvement plan generated by the audit, creating actionable tasks targeting RED and YELLOW tests to systematically remove tautologies and strengthen verification logic.
High coverage with missed production bugs usually indicates tautological tests and line hitters that inflate vanity metrics without verifying real logic. Auditing with SRE-level scrutiny traces call paths to expose these false confidence gaps.
zcaceresIdentify untested branches, error paths, and boundary conditions in test suites.
joshsymondsAudit test suites and categorize tests as RED, YELLOW, or GREEN.
obraValidate data flow at entry point, business logic, environment guards, and debug instrumentation.
summarybotngIntroduce code mutations and measure test suite kill rates.
