gk-test-audit

Audit unit tests and Storybook stories for low-value or brittle patterns.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/MartinoPolo/Grovekeeper --skill gk-test-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gk-test-audit
Source: https://github.com/MartinoPolo/Grovekeeper/tree/main/.agents/skills/gk-test-audit
Command: npx skills add https://github.com/MartinoPolo/Grovekeeper --skill gk-test-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you audit and improve a software test suite by identifying low-value, brittle, or redundant tests that slow development and reduce confidence in releases.

Core Features & Use Cases

  • Detect anti-patterns in tests: flags constant-shape assertions, brittle CSS class checks, type-check-only tests, mock-what-you-own, call-count assertions, and duplicate tests.
  • Enforce value-focused testing: prioritizes behavior tested through public APIs and assertions that describe requirements rather than implementation details.
  • Run a structured review and action workflow: discovers unit and Storybook play tests, evaluates them with consistent judging rules, compiles a report, confirms before changes, then executes safe deletions/improvements.

Quick Start

Ask: "Audit tests and improve test quality across unit and Storybook."

Frequently Asked Questions about gk-test-audit

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

FAQPage Schema
How do I identify and remove flaky tests from my unit test suite?

An automated test audit evaluates unit and Storybook play tests against explicit judging rules to identify low-value, brittle, or redundant tests. It generates a merged report with KEEP, REMOVE, IMPROVE, or DELETE decisions to clean up test quality and reduce flakiness.

How do I audit Storybook play functions for test quality and reliability?

Auditing Storybook play functions involves discovering the tests, evaluating them for anti-patterns like mock-what-you-own or call-count assertions, and confirming changes before execution. This structured review enforces value-focused testing through public APIs and improves overall suite reliability.

What are common test anti-patterns that reduce refactor safety?

Common test anti-patterns reducing refactor safety include type-check-only tests, constant-shape assertions, brittle CSS class checks, call-count assertions, and duplicate tests. These low-value tests prioritize implementation details over behavior tested through public APIs, slowing development and lowering release confidence.

Can I automatically delete low-value tests during ongoing development?

Yes, you can automatically delete low-value tests during ongoing development, but the workflow requires user confirmation before executing any safe deletions or improvements. After making changes, test verification runs to ensure the remaining suite maintains its integrity and refactor safety.

Does this test audit workflow require any specific testing frameworks or dependencies?

No specific testing frameworks or dependencies are required to run this test audit workflow. It applies to existing automated unit tests and Storybook stories with play functions, evaluating them based on explicit judging rules without needing external libraries or setup.