test-setup

Scaffold tests/ directory, engine-specific test runner config, and GitHub Actions workflow.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill test-setup-solace-ill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-setup
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/test-setup
Command: npx skills add https://github.com/solace-ill/vector-flow --skill test-setup-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold a complete test infrastructure for a software engine, including the tests/ directory, engine-specific test runner configuration, and a GitHub Actions workflow.

Core Features & Use Cases

  • Creates a standardized test layout (unit, integration, and smoke) and CI config.
  • Detects engine setup and existing state to prevent disruption; can regenerate missing pieces with a force option.
  • Works across engines and adapts to engine-specific runners and workflow hooks.

Quick Start

Run this once during the Technical Setup phase to scaffold the tests/ directory, engine-specific runners, and GitHub Actions workflow.

Frequently Asked Questions about test-setup

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

FAQPage Schema
How do I scaffold a test directory and CI workflow for a new engine?

To scaffold test infrastructure, this automation detects engine configuration, generates a standardized tests/ directory layout for unit, integration, and smoke tests, and wires GitHub Actions workflows without overwriting existing files.

What is the best way to automate GitHub Actions test runner configuration across different engines?

Automating GitHub Actions test runner configuration involves detecting engine-specific setups and generating missing workflow files. This scaffolding tool adapts to engine-specific runners and workflow hooks during the technical setup phase.

When should I initialize test infrastructure before the first sprint?

You should initialize test infrastructure during the Technical Setup phase before the first sprint. Running the scaffolding once creates the tests/ directory, engine-specific runners, and CI config without disrupting existing test setups.

Can I regenerate missing test files and CI config without overwriting existing items?

Yes, you can regenerate missing test files and CI config. The tool verifies existing test infrastructure and generates missing pieces for tests/ and .github/workflows/tests.yml safely, with a force option available to regenerate pieces if needed.

Does the test scaffolding work with engine configuration stored in technical preferences?

Yes, test scaffolding works by detecting engine configuration directly from .claude/docs/technical-preferences.md. It reads this file to adapt the test runner configuration and directory layout to the specific engine.

Why does test infrastructure scaffolding verify existing files before generating directories?

Test infrastructure scaffolding verifies existing files to prevent disruption to your current setup. By checking the existing state, it safely generates missing files for the tests/ directory and GitHub Actions workflow without overwriting your configurations.