test-setup

Scaffold automated testing infrastructure and CI/CD for a project engine.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill test-setup-carlosq96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-setup
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/test-setup
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill test-setup-carlosq96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold automated testing infrastructure and CI/CD for a project engine, saving setup time and ensuring consistent test gates.

Core Features & Use Cases

  • Detects the configured engine and creates a standard tests/ layout
  • Generates engine-specific test runners and a GitHub Actions workflow
  • Wires CI to run tests on every push and PR to main

Quick Start

Run this once during the Technical Setup phase to generate the tests/ structure and the .github/workflows/tests.yml file.

Frequently Asked Questions about test-setup

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

FAQPage Schema
How do I scaffold automated tests and CI workflows for a project engine?

Scaffolding automated tests generates a standard tests/ directory, engine-specific test runners, and a GitHub Actions workflow to run tests on push and PR to main.

What is engine detection and how does it work when setting up test runners?

Engine detection identifies your configured engine during the Technical Setup phase to generate the appropriate engine-specific test runners and standard directory layout.

How do I configure GitHub Actions to run automated tests on every push?

You configure GitHub Actions by generating a .github/workflows/tests.yml file that wires CI to run tests automatically on every push and PR to main.

Do I need engine configuration before generating a test directory and CI workflow?

Yes, engine configuration is required. The scaffolding process uses it to detect the engine and produce the correct test runners and GitHub Actions workflow.

What is the best way to set up consistent test gates for a new project engine?

Using automated scaffolding during the Technical Setup phase ensures consistent test gates by generating a standard tests/ layout and wiring CI to run on every push.