skills.rest
adisaputra10
adisaputra10COMMUNITY
Explore all skills by this author →
GitHub

reproduce-bug

Reproduce software bugs from ticket context and write failing regression tests.

Updated Aug 27, 2026
Search Tags:#testing#quality assurance#debugging#software development#regression testing#bug reproduction
One-click install
npx skills add https://github.com/adisaputra10/miidleware-n8n --skill reproduce-bug-adisaputra10
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/adisaputra10/miidleware-n8n/tree/main/.claude/skills/reproduce-bug
Command: npx skills add https://github.com/adisaputra10/miidleware-n8n --skill reproduce-bug-adisaputra10

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill systematically reproduces bugs reported in Linear tickets by creating failing regression tests, ensuring that the bug is well-defined and preventing regressions.

Core Features & Use Cases

  • Bug Reproduction: Analyzes ticket details to pinpoint the source of a bug.
  • Test Case Generation: Writes specific, failing tests to validate the bug's existence.
  • Root Cause Analysis: Helps identify the exact location and mechanism of the bug.
  • Use Case: A developer receives a Linear ticket describing a crash in the n8n execution engine. This Skill will analyze the ticket, identify the faulty code path, and generate a failing Jest integration test that demonstrates the crash, providing a clear report of the root cause and location.

Quick Start

Reproduce the bug described in the provided Linear ticket context.

Frequently Asked Questions about reproduce-bug

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

FAQPage Schema
How do I reproduce a software bug using a failing regression test?▼

To reproduce a software bug, this Skill systematically analyzes ticket context, traces code paths to locate source files, and generates failing regression tests that validate the bug's existence.

How do I find the root cause of a bug from a Linear ticket?▼

Finding a bug's root cause involves analyzing ticket signals to pinpoint the faulty code path, categorizing reproduction confidence, and generating a detailed report on the exact location and mechanism.

Can I generate Jest integration tests from a bug ticket description?▼

Yes, you can generate specific failing Jest integration tests by providing the Linear ticket context, which demonstrates the crash and validates the reported software bug.

What is the best way to prevent software regressions after fixing a bug?▼

The best way to prevent software regressions is creating failing regression tests that define the bug upfront, ensuring the issue remains fixed and well-defined throughout future development.

Does this bug reproduction approach work without specific dependencies?▼

Yes, this approach operates without external dependencies, systematically analyzing provided ticket context to locate source files and write failing tests regardless of your specific framework.

What level of bug reproduction confidence can I expect from automated test generation?▼

Automated test generation categorizes bug reproduction confidence by analyzing ticket signals and tracing code paths, providing detailed reports on root cause, location, and fix hints.

Related Skills

Explore More Software Engineering Skills→
Rub-gitRub-git

n8n:reproduce-bug

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

Community
Advanced
carlosamesarcarlosamesar
1

gd-debugger

Diagnoses software bugs and verifies minimal code changes with regression tests.

Community
Advanced
TestAny-ioTestAny-io
79

debug

Diagnose Testany test failures by analyzing execution logs and identifying root causes.

Official
Intermediate
kitfunsokitfunso

investigate

Guide root-cause debugging of software defects through symptom collection and hypothesis testing.

Community
Advanced