pipeline-test-runner

Name: pipeline-test-runner
Availability: InStock
Author: notque

Execute pipeline skills against real targets and generate per-subdomain pass/fail reports.

415|44|Updated Mar 18, 2026

Search Tags:#reports #orchestration #fixtures #parallel-execution #tests #artifact-validation #pipeline-testing

Ready to run

npx skills add https://github.com/notque/claude-code-toolkit --skill pipeline-test-runner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pipeline-test-runner
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/pipeline-test-runner
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill pipeline-test-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Validate that generated pipeline skills actually work by executing them against real targets. This phase ensures chains perform in practice, catching runtime issues missed by purely structural checks.

Core Features & Use Cases

Discover test targets (fixtures, codebase files, synthetic inputs) for subdomains
Run multiple subdomain skills in parallel and produce per-subdomain results
Validate dual-layer artifacts (manifest.json + content.md) and generate per-subdomain traces
Produce a dual-layer report consumable by pipeline-retro

Quick Start

Run the Pipeline Test Runner against a validated pipeline spec to execute tests and generate per-subdomain reports.

Frequently Asked Questions about pipeline-test-runner

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

FAQPage Schema

How do I validate generated pipeline skills against real targets?▼

To validate generated pipeline skills against real targets, you execute them using a validated pipeline spec JSON to discover test fixtures, run subdomain skills in parallel, and generate per-subdomain pass/fail reports.

What is pipeline testing with parallel execution and how does it work?▼

Pipeline testing with parallel execution runs multiple subdomain skills simultaneously against discovered test targets like codebase files and synthetic inputs, enforcing per-subdomain timeouts to catch runtime issues missed by structural checks.

How do I test pipeline fixtures and synthetic inputs for subdomains?▼

You test pipeline fixtures and synthetic inputs by running the test runner against a validated pipeline spec, which automatically discovers these test targets for each subdomain and executes the skills to measure runtime performance.

Does pipeline artifact validation check manifest.json and content.md files?▼

Yes, pipeline artifact validation checks dual-layer artifacts by validating manifest.json and content.md files using dedicated artifact validation scripts, generating per-subdomain traces to ensure generated pipelines produce expected outputs.

What is a dual-layer report for pipeline testing and when do I need it?▼

A dual-layer report for pipeline testing is a per-subdomain pass/fail output consumable by pipeline-retro, needed when you want to analyze runtime execution results and trace artifact validation failures after executing generated skills.