reproduce-bug-report-local

Reproduce logged-out Warp UI bugs using the exact reporter version.

6|Updated May 10, 2026

Search Tags:#version control #bug tracking #bug reproduction #Warp UI #repro workflow

Ready to run

npx skills add https://github.com/Luohao-Yan/warp-cn --skill reproduce-bug-report-local

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reproduce-bug-report-local
Source: https://github.com/Luohao-Yan/warp-cn/tree/main/.agents/skills/reproduce-bug-report-local
Command: npx skills add https://github.com/Luohao-Yan/warp-cn --skill reproduce-bug-report-local

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides specific guidance for reproducing bugs in the Warp UI while remaining logged out, catering to logged-out repros, exact reporter-version installations, and login-free onboarding.

Core Features & Use Cases

Specialized Bug Reproduction: Specializes the core reproduce-bug-report skill for logged-out Warp UI repros, exact reporter-version installs, and login-free onboarding.
Version Precision: Ensures reproduction against the exact Warp version/build and channel reported by the user.
Logged-Out Workflow: Maintains a logged-out Warp baseline for the repro attempt, adhering to login-free onboarding and avoiding authenticated flows.

Quick Start

Run the skill to reproduce the logged-out bug reported in the 'bug-1234' issue using the exact Warp version provided in the report.

Frequently Asked Questions about reproduce-bug-report-local

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

FAQPage Schema

How do I reproduce a Warp UI bug report while staying logged out?▼

Reproducing a logged-out Warp UI bug requires installing the exact Warp version and build channel reported by the user, maintaining an unauthenticated baseline state, and following specific reproduction steps while deliberately avoiding any login flows.

Why does my Warp UI bug reproduction fail when I am logged in?▼

Bug reproduction fails when logged in because the reported issue may only manifest in an unauthenticated state. You must maintain a logged-out baseline and adhere to login-free onboarding to trigger the exact conditions of the report.

What is the best way to ensure I am testing the exact Warp version from a bug report?▼

The best way to ensure version precision during bug tracking is to specialize your reproduction workflow by installing the exact Warp version, build, and channel specified in the user's bug report before attempting to replicate the issue.

Can I use a standard bug reproduction workflow for Warp UI onboarding issues?▼

You cannot use a standard workflow for logged-out Warp UI onboarding issues because this approach requires exact reporter-version installations and a strictly login-free onboarding path to accurately reproduce the unauthenticated bug state.

Do I need to install a specific Warp build to reproduce a logged-out bug?▼

Yes, you need to install the specific Warp build and channel reported by the user to ensure version precision. The bug reproduction process relies on matching the exact environment and version the reporter used.