skills.rest
Uguryldz
UguryldzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reproduce-bug

Reproduce reported bugs from Linear tickets with failing regression tests.

Updated Apr 9, 2026
Search Tags:#debugging#jest#linear#regression testing#playwright#n8n#bug reproduction
One-click install
npx skills add https://github.com/Uguryldz/n8nclean --skill reproduce-bug-uguryldz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/Uguryldz/n8nclean/tree/main/.claude/plugins/n8n/skills/reproduce-bug
Command: npx skills add https://github.com/Uguryldz/n8nclean --skill reproduce-bug-uguryldz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers often receive bug reports without a reliable way to confirm the defect before attempting a fix. This Skill systematically converts a Linear ticket's context into a failing regression test that proves the bug exists, preventing blind fixes and unverified patches. ## Core Features & Use Cases - Signal Extraction: Parses error messages, stack traces, reproduction steps, workflow JSON, and version info from ticket context. - Test Strategy Routing: Maps the affected area (nodes, execution engine, CLI/API, config, editor UI, E2E) to the correct test layer and framework such as Jest, Vitest, or Playwright. - Confidence Scoring: Classifies reproduction results as CONFIRMED, LIKELY, UNCONFIRMED, SKIPPED, or ALREADY_FIXED with a structured report including root cause, location, and fix hints. - Use Case: Given a Linear ticket reporting that a webhook trigger drops binary data, the Skill traces the code path, writes a failing Jest test in the appropriate package, and produces a reproduction report without modifying the source code. ## Quick Start Provide the full Linear ticket context including title, description, and comments, and ask to reproduce the reported bug with a failing test.

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 bug from a Linear ticket with a failing test?▼

Provide the full ticket context including title, description, and comments. The Skill extracts error signals, routes to the correct test layer, writes a regression test asserting correct behavior, and runs it to confirm the failure matches the hypothesis.

What test frameworks does bug reproduction use for different code areas?▼

Node operations use Jest with NodeTestHarness, the execution engine uses Jest integration tests with WorkflowRunner, the editor UI uses Vitest with Vue Test Utils, and E2E canvas scenarios use Playwright with test containers.

Does the bug reproduction skill fix the bug after reproducing it?▼

No, the Skill explicitly does not fix bugs. It only writes failing regression tests as evidence and provides a fix hint in the reproduction report, leaving the actual code changes to a separate step.

When does bug reproduction get skipped or marked unconfirmed?▼

Reproduction is skipped when it requires real third-party API credentials, race conditions, cloud infrastructure, or manual UI interaction. It is marked UNCONFIRMED after three failed attempts to trigger the failure.

What does the reproduction report include?▼

The report includes the ticket ID, confidence level (CONFIRMED, LIKELY, UNCONFIRMED, SKIPPED, or ALREADY_FIXED), root cause explanation, affected file locations with line numbers, failing test details, and a fix hint.

Related Skills

Explore More Software Engineering Skills→
greptileaigreptileai

reproduce-bug

Generate failing regression tests from Linear ticket bug reports.

Official
Advanced
ceedaragentsceedaragents
794

debug

Diagnose bugs through failing-test reproduction, root cause analysis, and minimal targeted fixes.

Official
Intermediate
ArangoGutierrezArangoGutierrez
3

go-review

Reviews Go code for error handling, concurrency, performance, and interface issues.

Community
Intermediate
CavellTopDevCavellTopDev

cloudflare-debug

Diagnose and fix Cloudflare Workers issues with structured debugging patterns.

Community
Intermediate