// Repo-specific bug reproduction guidance for Warp. Specializes the core reproduce-bug-report skill for logged-out Warp UI repros, exact reporter-version installs, and login-free onboarding.
| name | reproduce-bug-report-local |
| specializes | reproduce-bug-report |
| description | Repo-specific bug reproduction guidance for Warp. Specializes the core reproduce-bug-report skill for logged-out Warp UI repros, exact reporter-version installs, and login-free onboarding. |
warpThis file is a companion to the core reproduce-bug-report skill. It does not redefine the shared Oz computer-use orchestration, artifact handling, safety rules, or reporting format. It specializes scope and setup for Warp bug reports.
When applying the core skill to Warp, ensure the parent prompt and child prompts include:
unknown.Generate a reviewable changelog draft from PRs merged in a release range. Extracts explicit CHANGELOG markers, classifies unmarked PRs, adds external contributor attribution, and outputs markdown + JSON artifacts. Does NOT mutate channel_versions.json.
Launch two parallel Oz cloud agents with computer use to download and install the latest stable Linux Warp build, capture screenshots while walking through first-time onboarding in both logged-out and logged-in states, then selectively fan out follow-up cloud agents for distinct onboarding branches proposed by those initial explorers. Use this whenever the user asks to test, document, screenshot, or walk through the Warp first-time install/onboarding experience in a cloud Linux environment.
Turn rough feedback about the Warp app into a filed GitHub issue or duplicate-issue response for `warpdotdev/warp`. Use ONLY when the user explicitly wants to report a problem with the Warp terminal/IDE/app itself—not when they're working on their own code, managing their own GitHub repos, or doing general software development tasks. SKIP when: the user is creating/managing GitHub issues or PRs for their own projects, reviewing PRs, diagnosing CI failures, using `gh` CLI for repo management, or performing any GitHub workflow not specifically about reporting a problem with the Warp application itself.
Repo-specific review guidance for warp. Only the categories declared overridable by the core review-pr skill may be specialized here.
Reference guidance for classifying whether an unmarked PR should appear in the changelog and under which category. Used inline by the changelog-draft skill — not dispatched as a separate agent.
Create a one-time launch modal in the Warp client (feature announcement, onboarding, etc.). Use when adding a new modal that should appear exactly once per user on startup, gated by a feature flag, with colors sourced from Warp theme tokens and terminal theme colors.