review-testability

Name: review-testability
Availability: InStock
Author: doodledood

Detect testability anti-patterns in code and suggest refactorings.

4|1|Updated Jan 11, 2026

Search Tags:#anti-patterns #refactoring #testability #software-engineering #read-only #dependency-injection #code-design

Ready to run

npx skills add https://github.com/doodledood/codex-workflow --skill review-testability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-testability
Source: https://github.com/doodledood/codex-workflow/tree/main/skills/review-testability
Command: npx skills add https://github.com/doodledood/codex-workflow --skill review-testability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify testability bottlenecks in code by surfacing patterns that tie business logic to IO, hide dependencies, or rely on hard-coded instantiation, enabling safer, more maintainable designs.

Core Features & Use Cases

Read-only analysis: reviews code and provides findings without modifying source.
Anti-pattern detection: spots common testability issues such as implicit dependencies, global state, and constructor work.
Refactoring guidance: recommends patterns like functional core / imperative shell, explicit dependencies, and dependency injection to improve testability.
Scoped reviews: supports file-path or diff-based scope to target relevant changes and contexts.

Quick Start

Specify the files or directories to review, or provide a diff against origin/main to scope the analysis.

Frequently Asked Questions about review-testability

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

FAQPage Schema

How do I audit code for testability issues and hidden dependencies?▼

To audit code for testability, you review the source to locate patterns mixing business logic with IO, hidden dependencies, and hard-coded instantiation. This surfaces testability friction while preserving a read-only constraint on the source.

What are common testability anti-patterns in software engineering?▼

Common testability anti-patterns include implicit dependencies, global state, and constructor work. These patterns tie business logic to IO operations, making code difficult to test and maintain without structural refactoring.

How do I refactor code to separate business logic from IO operations?▼

Refactor code to separate business logic from IO by applying patterns like functional core and imperative shell. This design isolates pure logic from side effects, enabling safer unit testing and more maintainable code structures.

Can I scope a code review to specific files or a diff against origin/main?▼

Yes, you can scope a code review by specifying target file paths or providing a diff against origin/main. This targets relevant changes and contexts, ensuring the testability analysis focuses only on the specified code modifications.

Does dependency injection improve code testability?▼

Dependency injection improves testability by making dependencies explicit rather than hidden or hard-coded. This allows you to inject mock implementations during unit testing, isolating business logic from external IO operations and global state.