n8n:reproduce-bug

Reproduce bugs from Linear tickets by parsing contexts, writing regression tests, and executing them.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Rub-git/n8n-auto --skill n8n-reproduce-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n:reproduce-bug
Source: https://github.com/Rub-git/n8n-auto/tree/main/.agents/skills/reproduce-bug
Command: npx skills add https://github.com/Rub-git/n8n-auto --skill n8n-reproduce-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of reproducing bugs from Linear tickets with failing tests, reducing the time and effort required to diagnose and fix issues.

Core Features & Use Cases

  • Bug Reproduction: Automatically reproduce bugs from Linear tickets with failing tests.
  • Ticket Context Parsing: Extracts error messages, reproduction steps, and other relevant information from ticket contexts.
  • Test Strategy Routing: Routes the bug reproduction process to the appropriate test layer and pattern based on the affected area.
  • Source Code Locating: Locates the source code for the affected area to trace the code path and identify the bug.
  • Regression Test Writing: Writes a regression test that targets the specific hypothesis and asserts the correct behavior.
  • Test Execution and Scoring: Executes the test and classifies the result as confirmed, likely, unconfirmed, skipped, or already fixed.
  • Iterative Bug Reproduction: Iterates or bails on the bug reproduction process based on the test results.

Quick Start

Use the n8n:reproduce-bug skill to reproduce a bug from a Linear ticket with a failing test. Provide the full ticket context (title, description, comments) as input.

Frequently Asked Questions about n8n:reproduce-bug

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

FAQPage Schema
How do I automate bug reproduction from Linear tickets using regression tests?

Automate bug reproduction by parsing Linear ticket contexts to extract reproduction steps, routing the context to appropriate test strategies, writing regression tests, and executing them to confirm the bug. This systematic approach reduces manual diagnostic effort for software engineering teams.

What is the process for converting a Linear ticket into a failing test?

Converting a Linear ticket into a failing test involves parsing ticket contexts for error messages, locating the affected source code, writing a regression test that asserts correct behavior, and executing it to classify the bug as confirmed, likely, unconfirmed, skipped, or already fixed.

How does test strategy routing work for bug reproduction in software engineering?

Test strategy routing directs the bug reproduction process to the appropriate test layer and pattern based on the affected code area. It traces the code path by locating the source code, ensuring the regression test targets the specific bug hypothesis.

Can I use this bug reproduction approach if I only have a ticket title and description?

Bug reproduction requires the full ticket context, including the title, description, and comments, as input. Providing complete context ensures accurate extraction of reproduction steps and error messages needed to write effective regression tests.

What happens when a regression test fails to confirm the bug during iterative reproduction?

During iterative bug reproduction, the process bails or iterates based on test execution results. If the test does not confirm the bug, the system classifies the result as unconfirmed, likely, skipped, or already fixed to guide further diagnostic action.