
Reproduce Bug
This is a structured framework for turning Linear bug tickets into failing regression tests for n8n workflows. It walks through parsing ticket signals, routing to the right test layer (Jest unit, integration, Vitest, or Playwright), tracing the code path, and writing a test that proves the bug exists without fixing it. The routing table is smart, mapping affected areas like nodes, triggers, or UI components to specific test patterns and locations. It knows when to bail (needs real API credentials, race conditions, cloud infrastructure) and outputs a confidence score from CONFIRMED to SKIPPED. Honestly most useful if you're maintaining n8n itself or a large fork, since it's tailored to their package structure and testing conventions. Saves you from the "where do I even start" paralysis when facing a vague bug report.
- skills.sh installs
- 306
- GitHub stars
- 210K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add n8n-io/n8n --skill reproduce-bug --agent claude-codeInstalls into .claude/skills of the current project.
Files
Bug Reproduction Framework
Given a Linear ticket context ($ARGUMENTS), systematically reproduce the bug with a failing regression test.
Step 1: Parse Signals
Extract the following from the provided ticket context:
- Error message / stack trace (if provided)
- Reproduction steps (if provided)
- Workflow JSON (if attached)
- Affected area (node, execution engine, editor, API, config, etc.)
- Version where it broke / last working version
Step 2: Route to Test Strategy
Based on the affected area, pick the test layer and pattern:
Sponsors
Details
- Repository
- github.com/n8n-io/n8n
- Categories
- Testing & QA, Debugging, Automation & Workflows
- First seen
- Jun 3, 2026