How does this skill prevent production code pollution?

It identifies methods intended only for test cleanup or setup and suggests moving them to external test utility files rather than including them in production classes.

What are the Iron Laws of testing enforced by this skill?

The skill enforces three core rules: NEVER test mock behavior, NEVER add test-only methods to production classes, and NEVER mock without fully understanding dependencies.

Why shouldn't I test mock behavior?

Testing mock behavior verifies that your test setup works but tells you nothing about the actual code. This skill helps you focus on asserting real component outcomes.

Does this skill work with TDD?

Yes, it is designed to complement TDD by ensuring you write failing tests against real behavior before introducing minimal, necessary mocking.

Testing Anti-Pattern Guard

Name: Testing Anti-Pattern Guard
Author: flora131

byflora131

•

Security & Testing

Prevents common testing pitfalls like mock-centric assertions and production code pollution to ensure reliable, behavior-driven test suites.

The Testing Anti-Pattern Guard skill acts as an automated architectural reviewer for your test suites. It enforces strict 'Iron Laws' of testing to ensure that assertions verify real application behavior rather than the mechanics of mocks. By implementing standardized gate functions, the skill prevents developers from polluting production code with test-only methods, creates more resilient mocks that mirror real API structures, and ensures that side effects are fully understood before isolation. It is an essential tool for teams practicing Test-Driven Development (TDD) who want to avoid fragile, high-maintenance tests.

Key Features

01Provides Gate Functions to validate the necessity and depth of mocks

02Promotes TDD workflows to ensure tests are never an afterthought

03Enforces 'Iron Laws' to prevent testing mock behavior instead of real logic

04Mandates complete API mirroring to prevent silent failures from partial mocks

05Identifies and blocks test-only methods from leaking into production classes

0656 GitHub stars

Use Cases

01Ensuring new developers follow consistent, high-quality mocking patterns

02Refactoring fragile test suites that break when implementation details change

03Cleaning up production codebases polluted with test-specific lifecycle methods

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add flora131/atomic testing-anti-patterns

For use in Claude.ai and ChatGPT

Download Skill