openmates:reproduce-first

Require a failing end-to-end spec that reproduces a reported bug before writing fix code.

43|2|Updated Jan 25, 2024
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill openmates-reproduce-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openmates:reproduce-first
Source: https://github.com/glowingkitty/OpenMates/tree/main/.claude/skills/reproduce-first
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill openmates-reproduce-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents fixing the wrong thing by requiring a failing end-to-end spec that reproduces the user-visible bug before any code changes are made.

Core Features & Use Cases

  • Linear-context reproduction: When given a Linear issue ID (like OPE-123), it pulls full issue context (images and comments) and guides you through the Linear pickup workflow.
  • Spec coverage decisioning: It checks for an existing E2E spec for the area, extends it with a targeted assertion when needed, or proposes a minimal new spec when none exists.
  • RED-to-GREEN enforcement: It runs the spec and requires it to fail (red) before any fix code is written, then requires the same spec to pass (green) after the fix.

Quick Start

Use openmates:reproduce-first with the bug’s Linear issue id or a short description of the incorrect user-visible behavior to create and run a failing reproduction spec.

Frequently Asked Questions about openmates:reproduce-first

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

FAQPage Schema
How do I enforce a test-first workflow for e2e bug reproduction?

To enforce a test-first workflow for e2e bug reproduction, you must create and run a failing end-to-end spec that replicates the user-visible bug before writing any fix code, ensuring the spec passes after the fix.

How do I reproduce a Linear issue bug using Playwright?

You can reproduce a Linear issue bug by providing the issue ID to extract full context, locating or proposing a Playwright e2e spec, and running it to confirm the test fails before applying any code fixes.

What is the red green testing process for user-visible regressions?

The red green testing process for user-visible regressions requires running an e2e spec to confirm it fails red before a fix, then executing the same spec to verify it passes green after the code change.

Can I use a test-first approach with a free-text bug description instead of a Linear issue?

Yes, you can use a test-first approach with a free-text bug description, guiding the workflow to check for existing e2e specs, extend them with targeted assertions, or propose minimal new specs to reproduce the behavior.

When should I not use a test-first bug reproduction workflow?

You should not use a test-first bug reproduction workflow for non-user-visible behavior regressions, as it specifically targets end-to-end spec validation for user-facing bugs using the repository's test runner.

What is the best way to prevent fixing the wrong bug in end-to-end testing?

The best way to prevent fixing the wrong bug in end-to-end testing is to require a failing e2e spec that reproduces the user-visible issue before any code changes are made, enforcing strict red-to-green validation.