test-helpers

Generate reusable test helper libraries from existing test patterns and project preferences.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill test-helpers-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-helpers
Source: https://github.com/dnkrow/skill/tree/main/claude-global/test-helpers
Command: npx skills add https://github.com/dnkrow/skill --skill test-helpers-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing repetitive test setup, assertions, and mocks takes time and makes your test suite inconsistent across systems and engines.

Core Features & Use Cases

  • Engine- and framework-aware helpers: Generates tailored helpers by detecting the configured engine, language, and testing framework from project technical preferences.
  • Pattern-aligned test generation: Scans existing tests to reuse your current setup/fixture, assertion, object creation, and mocking patterns rather than using a generic template.
  • System-scoped helper libraries: Produces system-specific factories for scenarios driven by your GDDs and test expectations, reducing boilerplate when writing new tests.

Quick Start

Run /test-helpers scaffold first, then run /test-helpers all to generate the full set of engine- and system-specific helpers for your test suite.

Frequently Asked Questions about test-helpers

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

FAQPage Schema
How do I generate reusable test helpers to eliminate repetitive setup and mocking across my test suites?

To generate reusable test helpers, use the scaffolding command to analyze your project's technical preferences, scan existing test files for recurring setup and mocking patterns, and output system-specific factory libraries into your tests/helpers directory.

Can I automatically create test helpers that match my existing test framework and engine setup?

Yes, test helper generation detects your configured engine, language, and testing framework from project technical preferences, then scans existing tests to reuse your current setup, assertion, object creation, and mocking patterns rather than applying generic templates.

How do I scaffold test helpers for domain systems defined in my game design documents?

To scaffold test helpers for GDD-defined domain systems, parse the GDD system definitions and registry mappings, then generate system-scoped factory libraries tailored to those specific scenarios and test expectations without overwriting existing files.

What's the best way to reduce boilerplate when adding new test coverage for combat or other domain systems?

The best way to reduce boilerplate is generating system-specific helper libraries that standardize setup, assertions, and mocks for domain systems, allowing new tests to reuse established patterns rather than repeating manual configuration.

Does generating engine-specific test helpers overwrite my existing test files?

No, generating engine-specific test helpers writes outputs into tests/helpers/ and tests/helpers/[system]_factory equivalents without overwriting existing files, preserving your current test suite while adding new system-scoped factories.

When do I need to scaffold a new test framework versus generating individual test helpers?

Scaffold a new test framework when starting from scratch or adding broad system test coverage, then generate individual test helpers when multiple tests share common setup, assertion, or mocking patterns that need standardization.