reproduce-bug-report-local

Reproduce logged-out Warp UI and interaction bugs using the reporter's exact version.

88|19|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Heartcoolman/warp-cn --skill reproduce-bug-report-local-heartcoolman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reproduce-bug-report-local
Source: https://github.com/Heartcoolman/warp-cn/tree/main/.agents/skills/reproduce-bug-report-local
Command: npx skills add https://github.com/Heartcoolman/warp-cn --skill reproduce-bug-report-local-heartcoolman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users reproduce and report bugs in the Warp application while remaining logged out, focusing on UI and interaction bugs.

Core Features & Use Cases

  • Specialized Bug Reproduction: Provides specific guidance for reproducing bugs in the logged-out state of Warp.
  • Scope Definition: Outlines the types of bugs suitable for this skill, such as UI, interaction, and logged-out onboarding issues.
  • Version and Install Strategy: Instructs on using the exact Warp version and build reported by the user for accurate reproduction.
  • Logged-out Environment: Ensures Warp remains logged out during the reproduction process, adhering to a logged-out baseline.

Quick Start

Use the reproduce-bug-report-local skill to set up a logged-out Warp environment and attempt to reproduce the bug you are experiencing.

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 Warp UI bugs in a logged-out environment?

To reproduce Warp UI bugs in a logged-out environment, isolate the issue by ensuring the application remains logged out while focusing on interaction and onboarding problems. This method targets UI anomalies without user-specific configuration interference.

What types of Warp interaction issues can I reproduce while logged out?

You can reproduce Warp interaction issues related to the logged-out UI state, including onboarding flows and general interface bugs. The process specifically targets problems visible before user authentication.

Do I need a specific Warp version to reproduce reported UI issues?

Yes, you need the exact Warp version and build channel reported by the user to reproduce UI issues accurately. Matching the reported version ensures the logged-out environment reflects the exact conditions where the bug occurred.

What is the best way to isolate a Warp bug report locally?

The best way to isolate a Warp bug report locally is to set up a logged-out environment using the user's reported version. This ensures you focus on UI and interaction issues without account-specific data interference.

Why does my Warp bug reproduction fail when logged in?

Warp bug reproduction may fail when logged in because user-specific settings and configurations can mask UI issues. Reproducing the bug in a logged-out environment isolates the baseline interaction problems.