reproduce-bug

Generate a failing regression test from Linear ticket context.

Updated Mar 20, 2026

Search Tags:#debugging #reproduce #ci #bug #regression-test #test-strategy #linear-ticket

Ready to run

npx skills add https://github.com/Noyoucringe/n8n-workflow --skill reproduce-bug-noyoucringe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/Noyoucringe/n8n-workflow/tree/main/.claude/skills/reproduce-bug
Command: npx skills add https://github.com/Noyoucringe/n8n-workflow --skill reproduce-bug-noyoucringe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce a bug from a Linear ticket context by generating a regression test that fails, using the full ticket details (title, description, comments) as input.

Core Features & Use Cases

Parse the provided Linear ticket context to extract error signals, reproduction steps, and related workflow data.
Route to an appropriate test strategy across node/CI environments, including unit and integration levels.
Create a structured regression test that captures the bug scenario and includes a happy-path where applicable.

Quick Start

Provide the Linear ticket context to automatically generate a failing regression test that reproduces the bug.

Frequently Asked Questions about reproduce-bug

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

FAQPage Schema

How do I generate a regression test from a Linear ticket to reproduce a bug?▼

Generating a regression test from a Linear ticket requires providing the full ticket context including title, description, and comments. The system extracts error signals and reproduction steps to produce a structured failing test artifact for CI.

What signals are needed to write a failing regression test for a bug ticket?▼

Writing a failing regression test requires error signals, reproduction steps, and related workflow data extracted from the Linear ticket context. These signals route to an appropriate test strategy across node and CI environments to capture the bug scenario.

How do I create a regression test that captures both a bug scenario and a happy-path?▼

Creating a regression test that captures a bug scenario and a happy-path requires routing to an appropriate test strategy based on extracted ticket signals. The system produces a structured test artifact that includes the happy-path where applicable.

Can I use a regression test strategy across node and CI environments for bug reproduction?▼

Yes, you can use a regression test strategy across node and CI environments for bug reproduction. The system routes extracted Linear ticket context to an appropriate test strategy, including unit and integration levels, to produce CI-ready test artifacts.

What is the best way to parse Linear ticket comments for bug reproduction steps?▼

The best way to parse Linear ticket comments for bug reproduction steps is to process the full ticket context. The system operates on the title, description, and comments to extract error signals and related workflow data to select the correct test strategy.

When should I not use an automated regression test for a bug ticket?▼

You should not use an automated regression test for a bug ticket when the provided Linear ticket context lacks sufficient error signals or reproduction steps. Without clear workflow data and descriptions, the system cannot effectively route to a structured test strategy.