
Reproduce Bug Report
Launches Oz cloud agents with computer use to reproduce UI bugs from GitHub issues, Linear tickets, or support reports. The parent agent reads the bug report, extracts environment details and repro steps, then spins up one or more cloud agents to actually interact with the app and capture screenshots. If the steps are vague, it can launch multiple agents testing different hypotheses like OS variants or fresh versus configured state. The child agents follow a disciplined workflow: install the reporter's exact version when possible, document what they tried in a manifest, take ordered screenshots at each step, and report clear evidence instead of guessing. The safety guardrails are thorough, no posting comments externally, no leaking tokens in screenshots, no signing into accounts unless explicitly authorized. This is the infrastructure play for visual bug triage at scale.
- skills.sh installs
- 27K
- GitHub stars
- 684
- last updated
- Aug 21, 2026
Install
$ npx -y skills add warpdotdev/common-skills --skill reproduce-bug-report --agent claude-codeInstalls into .claude/skills of the current project.
Files
Reproduce bug report
Use this skill when the current context is a GitHub issue, support report, Linear ticket, or user prompt describing a specific bug that may be reproduced through visible application behavior. It is primarily for UI, rendering, windowing, settings, editor, terminal-display, onboarding, or other interactive bugs where a screen recording (or screenshots) makes the result more actionable.
The parent agent should not try to manually reproduce the UI bug locally unless the user explicitly asks. Launch one or more Oz cloud agents with computer use enabled so they can run the relevant app, interact with it, and capture visual evidence.
Parent workflow
Sponsors
Details
- Repository
- github.com/warpdotdev/common-skills
- Categories
- Frontend Development, Git & Pull Requests, AI & Agent Building, Debugging, Cloud & Infrastructure, Design & UI/UX, CLI & Terminal, Video & Audio Editing
- First seen
- Jul 14, 2026
More from warpdotdev/common-skills
All 23- Respond To Pr Comments In Blocklist25.3K
- Validate Changes Match Specs25.3K
- Cross Critique22.1K
- Research22K
- Saga20.8K
- Write Feature Docs19.3K
- Scan New Specs19.3K
- Readout17.7K
- Review Pr29.1K
- Spec Driven Implementation28.9K
- Write Product Spec28.9K
- Write Tech Spec28.8K
- Resolve Merge Conflicts28.8K
- Fix Errors28.7K
- Implement Specs28.7K
- Create Pr28.7K
- Update Skill28.6K
- Diagnose Ci Failures28.6K
- Pr Walkthrough28.3K
- Brandalf28.3K
- Council28.1K
- Check Impl Against Spec27.1K