gui-reproduce-bug-report-local

Reproduces logged-out Warp GUI bug reports using exact reporter-version Linux builds.

64.7k|5.5k|Updated Jul 8, 2021
One-click install
npx skills add https://github.com/warpdotdev/warp --skill gui-reproduce-bug-report-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gui-reproduce-bug-report-local
Source: https://github.com/warpdotdev/warp/tree/main/.agents/skills/gui-reproduce-bug-report-local
Command: npx skills add https://github.com/warpdotdev/warp --skill gui-reproduce-bug-report-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug reports for the Warp GUI desktop app are hard to verify when the reporter's exact version, platform, and app state are unknown. This Skill specializes the core reproduce-bug-report workflow so agents can deterministically reproduce logged-out Warp UI bugs against the exact reporter-version build.

Core Features & Use Cases

  • Exact Version Matching: Installs the precise Warp Linux package or binary matching the reporter's version, build, and channel instead of defaulting to the latest stable release.
  • Logged-Out Reproduction Baseline: Keeps Warp logged out, completes the login-free onboarding path, and captures a baseline screenshot before attempting reproduction.
  • Scoped Bug Coverage: Handles UI-visible, interaction, rendering, layout, onboarding, settings, and terminal-display bugs while explicitly blocking authenticated or cloud-synced flows.
  • Use Case: A user reports a settings panel rendering glitch on Warp v0.2024.x for macOS. The agent installs the matching Linux build as a proxy, launches logged-out Warp, follows the report's exact steps, and records versions, fallback decisions, and screenshots in the final report.

Quick Start

Reproduce this Warp GUI bug report locally using the exact reporter version while keeping the app logged out, and document the installed build and results.

Frequently Asked Questions about gui-reproduce-bug-report-local

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

FAQPage Schema
How do I reproduce a Warp GUI bug report locally?

Install the exact Warp Linux package matching the reporter's version and channel, launch Warp logged out, complete the login-free onboarding, then follow the report's exact steps. Capture a baseline screenshot and record all version details in the final report.

How do I install a specific Warp version for bug reproduction?

Use the repository's release tooling or docs to find and install the exact versioned Linux package or binary matching the reporter's build and channel. Do not silently substitute the latest stable build when an exact artifact exists.

Can I reproduce macOS or Windows Warp bugs on Linux?

Yes, use the corresponding Linux build from the same version and channel as a proxy when a matching Linux artifact exists. State clearly in the report that the test was a Linux proxy for the reporter's platform.

Does this workflow support logged-in or account-specific Warp bugs?

No, the workflow only covers bugs reproducible while Warp remains logged out. Authenticated flows, account state, cloud sync, and AI features requiring login are out of scope and must be reported as blocked.

What if the exact reporter Warp version cannot be installed?

Report the failure clearly, explain what was attempted, and use the closest justified fallback only when useful for the investigation. Record the requested version, installed version, artifact source, and fallback decision in the manifest.