How does this skill help with incomplete mocks?

It provides a gate function that requires you to verify real API response structures, ensuring your mocks contain all necessary fields used by downstream code to prevent silent failures.

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

The Iron Laws are: 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 only verifies that your mock setup works; it tells you nothing about the actual logic of your application, leading to false confidence and brittle tests.

How does this skill prevent production code pollution?

It identifies methods that are only used in test suites and guides you to move them into dedicated test-utility files rather than leaving them in production classes.

Testing Anti-Patterns Guard

Name: Testing Anti-Patterns Guard
Author: apexbusiness-systems

byapexbusiness-systems

0•

Security & Testing

Eliminates common testing mistakes by enforcing strict TDD principles and preventing mock-related technical debt.

Testing Anti-Patterns Guard is a specialized Claude Code skill designed to improve software quality by identifying and preventing common pitfalls in unit and integration testing. It enforces the 'Iron Laws' of testing—ensuring mocks are used for isolation rather than verification—and prevents production code pollution by keeping test-only logic in utility files. By guiding developers through TDD cycles and providing 'Gate Functions' before mocking, it ensures that tests verify real business behavior while maintaining complete, accurate data structures.

Key Features

01Provides gate functions to validate the necessity of mocks

02Prevents 'test-only' method pollution in production classes

030 GitHub stars

04Identifies and fixes incomplete or partial mock data structures

05Promotes strict Test-Driven Development (TDD) workflows

06Enforces behavior-driven testing over mock verification

Use Cases

01Refactoring legacy tests to ensure they verify real logic instead of mock existence

02Debugging mysterious test failures caused by over-mocking or side-effect ignorance

03Cleaning up production classes by moving test-specific methods to external utilities

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add apexbusiness-systems/apex-omnihub testing-anti-patterns

For use in Claude.ai and ChatGPT

Download Skill