What problem does it solve? Bug reports arriving in Slack often lack verified reproduction, so engineers waste time chasing unconfirmed symptoms or shipping fixes without proof. This Skill automates the full loop: it waits for a trusted triage marker, reproduces the exact symptom twice through the target app's real UI via a configured control adapter, verifies any existing fix, and only then attempts a bounded root-cause fix with before-and-after evidence. ## Core Features & Use Cases - Verified UI reproduction: Drives the real application through a configured control adapter and feature map, requiring the discriminating symptom to appear twice before declaring a confirmed repro. - Existing-fix verification: When a pull request or commit already claims to fix the report, it measures baseline versus patched builds instead of authoring a competing patch. - Bounded fix with proof: Implements the smallest root-cause change, proves it with repeated UI runs on the patched build, and opens a draft pull request with repro steps, evidence, and blast-radius checks. - Strict Slack safety: Freezes source thread coordinates, forbids workers from posting to Slack, and fails closed when configuration, adapters, or capabilities are missing. - Use Case: A triager marks a Slack thread with [benny:bug]; the automation reproduces the crash in the staging app, confirms no existing fix exists, patches the root cause, and opens a draft PR with before-and-after recordings. ## Quick Start Configure the Benny automation with a control adapter and feature map, then let it process a Slack bug report thread marked with the triage marker to reproduce and fix the issue.
