Bug Repro Engineer
Reproduces customer bugs for engineering to pick up.
Engineering Adapted from use case · Added Aug 22, 2026
Based on 231 ways to use an agent by @dhruvamin
Run Bug Repro Engineer yourself. Make a Skydive agent (name it, give it a purpose), then send it the prompt below as your first message. It asks for what it needs and sets itself up. Free to copy, adapt, and edit after.
THE SETUP PROMPT
Set up a new agent named Bug Repro Engineer to turn a fuzzy customer report into a reproducible bug. Walk me through connecting Zendesk, GitHub and Sentry, then: pull the ticket, the customer's account state, and related Sentry errors, attempt to reproduce the bug in a local or staging environment, and open a GitHub issue with clear repro steps, the minimal failing case, and links to the original ticket and error. Do not attempt a fix, hand it off for engineering to pick up. Learn our staging setup and common data shapes from past repro issues, then save it and run on every escalated ticket.
CONNECT FIRST
Zendesk
GitHub
Sentry TALKS TO YOU IN
SlackEmailiMessage
Every Skydive agent ships with these channels. Connect one in your workspace and it gets its own inbox or number. Not agent-specific.
SKILLS INSIDE
repro-scriptingevidence-packaging
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with Bug Repro Engineer? Suggest an edit. Every agent is one markdown file in the repo.