ln-635-test-isolation-auditor

Audit test suites for isolation violations, determinism issues, and anti-patterns.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-635-test-isolation-auditor-cbbkrd-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-635-test-isolation-auditor
Source: https://github.com/cbbkrd-tech/jl-finishes/tree/main/.claude/skills/ln-635-test-isolation-auditor
Command: npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-635-test-isolation-auditor-cbbkrd-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill rigorously audits your test suites to ensure they are properly isolated from external dependencies and free from common anti-patterns, leading to more reliable and maintainable code.

Core Features & Use Cases

  • Test Isolation Audit: Checks for proper mocking of APIs, databases, file systems, time, random number generation, and network calls.
  • Determinism Checks: Identifies flaky tests, time-dependent assertions, order-dependent tests, and shared mutable state issues.
  • Anti-Pattern Detection: Flags tests that are too large, always pass without assertions ('Liar'), only test the 'happy path', or test framework behavior instead of business logic.
  • Use Case: Before merging a critical feature, run this Skill to automatically scan all related unit and integration tests, receiving a detailed report on potential issues and a compliance score.

Quick Start

Use the ln-635-test-isolation-auditor skill to audit the test suite located in the current directory.

Frequently Asked Questions about ln-635-test-isolation-auditor

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

FAQPage Schema
How do I detect flaky tests caused by shared mutable state or order dependencies?

Detect flaky tests by auditing your test suite for shared mutable state, order dependencies, and improper isolation from external APIs, databases, and file systems. The audit identifies determinism issues and generates a detailed JSON report with severity findings and recommendations.

What are common test anti-patterns like 'The Liar' and 'Happy Path Only'?

Common test anti-patterns include 'The Liar' where tests always pass without assertions, 'The Giant' for overly large tests, and 'Happy Path Only' which skips edge cases. Auditing flags these patterns, alongside testing framework behavior instead of business logic, to improve reliability.

How to audit test isolation for external APIs and database interactions?

Audit test isolation by scanning your test suite to verify proper mocking of external APIs, databases, file systems, time, random number generation, and network calls. The process checks for isolation violations and outputs a compliance report with actionable recommendations.

Why does my test suite pass locally but fail during continuous integration?

Your test suite may fail in CI due to determinism issues like time-dependent assertions, uncontrolled random number generation, or unmocked network interactions. Auditing the tests identifies these isolation violations and anti-patterns causing inconsistent execution results.

Can I scan an existing project directory for test determinism issues?

Yes, you can scan an existing project by running the audit against the test suite located in your current working directory. It automatically analyzes the tests for isolation violations and anti-patterns, providing a detailed JSON report of findings.