reproduce-and-fix-issues

Reproduce triaged Slack bugs through real UI interaction and open verified draft pull requests.

6.6k|542|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cursor/plugins --skill reproduce-and-fix-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reproduce-and-fix-issues
Source: https://github.com/cursor/plugins/tree/main/pstack/automations/benny/skills/reproduce-and-fix-issues
Command: npx skills add https://github.com/cursor/plugins --skill reproduce-and-fix-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bug reports arriving in Slack often lack verified reproduction steps, and fixes get shipped without proof they resolve the actual symptom. This Skill enforces a disciplined workflow that reproduces triaged bugs through a configured app-control adapter, verifies existing fixes, and only opens a bounded draft pull request after before-and-after evidence is captured.

Core Features & Use Cases

  • Triage-gated reproduction: Waits for a trusted [benny:bug] or [benny:performance] marker from a configured triage identity before doing any work, and fails closed when configuration, control adapter, or feature map is missing.
  • Real UI verification: Drives the target app through clicks, typing, and navigation via a control adapter contract, requiring the discriminating symptom to appear twice with screenshot and recording evidence.
  • Bounded fix workflow: Verifies existing pull requests against baseline and patched builds, or authors a root-cause fix with TDD guidance, then opens a draft pull request only after before-and-after proof.
  • Use Case: A triager marks a Slack thread with [benny:bug]. The automation reproduces the crash in the app UI twice, confirms no existing fix exists, implements a minimal root-cause patch, proves the fix with repeat UI runs, and opens a draft PR linking the tracker issue.

Quick Start

Configure the Benny automation with a control adapter and feature map, then post a [benny:bug] marker in a triaged Slack thread to trigger reproduction and a verified draft pull request.

Frequently Asked Questions about reproduce-and-fix-issues

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

FAQPage Schema
How do I automatically reproduce bugs reported in Slack?

Configure the Benny automation with a control adapter and feature map, then have a trusted triager post a [benny:bug] or [benny:performance] marker in the source thread. The skill drives the app's real UI to reproduce the symptom twice before taking further action.

How does the skill verify an existing fix before writing a new one?

It switches to verify mode when an open pull request or merged commit plausibly fixes the report. It runs the reported UI path on both the baseline and patched builds twice, confirming the symptom appears on baseline and disappears on the patched build.

What is a control adapter and why is it required?

A control adapter is a user-configured skill that implements seven capabilities: bring up the app, drive the UI, drive mapped features, inspect state, screenshot, record, and clean up. Without it or a completed feature map, the workflow fails closed and does nothing.

Can the automation post messages to Slack on its own?

Only the coordinator posts to Slack, and never a root message in the source channel. Delegated workers are read-only, every child prompt forbids Slack write actions, and a code-editing worker only runs when its environment provably excludes Slack credentials.

When does the skill refuse to open a pull request?

It stops without a pull request when the symptom does not reproduce twice, a person claims the fix, an existing fix artifact exists, the root cause is unconfirmed, or the change exceeds the configured effort budget. A draft PR requires before-and-after UI evidence.