skills.rest
greptileai
greptileaiOFFICIAL
Explore all skills by this author →
Website𝕏@greptileGitHub

reproduce-bug

Generate failing regression tests from Linear ticket bug reports.

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

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 root cause is identified and verifiable.

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.
  • Use Case: A user reports a bug in a specific n8n node. This Skill will analyze the ticket, locate the relevant code, write a test that fails due to the bug, and provide a report on the findings.

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 generate failing regression tests from bug ticket descriptions?▼

You can generate failing regression tests by providing bug ticket context, error messages, and reproduction steps. The Skill analyzes the affected areas, traces code paths, and writes a failing test using established patterns to verify the bug.

What is the best way to reproduce a software bug with a test case?▼

The best way to reproduce a software bug is to analyze ticket details to pinpoint the source, form hypotheses about the code path, and write a specific failing test. This validates the bug and classifies the reproduction confidence in a detailed report.

Can I use bug reproduction to locate source files from error messages?▼

Yes, you can use bug reproduction to locate source files from error messages. The Skill analyzes error messages and reproduction steps to route to appropriate test strategies and traces the code paths to find the exact source files affected.

Does this approach work for regression testing in software development?▼

Yes, this approach works for regression testing in software development. It systematically reproduces reported bugs by creating failing regression tests, ensuring that the root cause is identified, verifiable, and documented with a confidence classification.

How do I trace code paths to write a failing test for a reported bug?▼

To trace code paths and write a failing test, the Skill analyzes the provided ticket context, forms hypotheses about the failure, locates the relevant source files, and applies established test patterns to generate a test that fails due to the bug.

What are the limitations of automated bug reproduction from ticket context?▼

A limitation of automated bug reproduction is that it relies on the completeness of the provided ticket context, error messages, and reproduction steps. It classifies reproduction confidence, indicating that complex or vaguely described bugs may result in lower confidence levels.

Related Skills

Explore More Software Engineering Skills→
yunseo-kimyunseo-kim
1

reproduce-bug

Generate failing regression tests from bug tickets and code analysis.

Community
Advanced
seokan-jeongseokan-jeong
8

team-shinchan:test-driven-development

Enforce test-first development with failing tests before production code.

Community
Intermediate
FlexNetOSFlexNetOS

code-research-verify

Verify code-analysis claims against actual source code.

Official
Advanced
joshribakoffjoshribakoff
2

debugging

Automate methodical debugging workflows to isolate root causes in software projects.

Community
Advanced