skills.rest
pathtoresiliencebv
pathtoresiliencebvCOMMUNITY
Explore all skills by this author →
GitHub

reproduce-bug-report-local

Reproduce logged-out Warp UI bugs with exact reporter-version installs.

Updated Jun 20, 2026
Search Tags:#debugging#issue tracking#bug reproduction#Warp UI#logged-out workflow
One-click install
npx skills add https://github.com/pathtoresiliencebv/warp-customized --skill reproduce-bug-report-local-pathtoresiliencebv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reproduce-bug-report-local
Source: https://github.com/pathtoresiliencebv/warp-customized/tree/main/.agents/skills/reproduce-bug-report-local
Command: npx skills add https://github.com/pathtoresiliencebv/warp-customized --skill reproduce-bug-report-local-pathtoresiliencebv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill guides the reproduction of bugs specific to the Warp UI while logged out, ensuring accurate debugging and issue reports.

Core Features & Use Cases

  • Specialized Bug Reproduction: Provides detailed instructions for reproducing logged-out Warp UI bugs.
  • Version Matching: Ensures the exact Warp version is used for accurate reproduction.
  • Logged-Out Workflow: Ensures the reproduction process remains logged out for consistency.
  • Use Case: When a user encounters a bug in the Warp UI, this Skill helps them reproduce the issue in a logged-out state, providing the necessary information for debugging.

Quick Start

Use the reproduce-bug-report-local skill to reproduce a logged-out bug in Warp UI.

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 while logged out?▼

To reproduce a logged-out Warp UI bug, this skill guides you through installing the exact reporter Warp version and executing a login-free workflow to consistently trigger the UI issue for accurate debugging.

Why does bug reproduction require matching the exact reporter version?▼

Bug reproduction requires matching the exact reporter version because UI behaviors and logged-out states can vary across releases. Installing the specific Warp version ensures the issue is accurately replicated for debugging.

Can I use this workflow for logged-in Warp UI issues?▼

No, this workflow is specifically specialized for logged-out Warp UI scenarios. It focuses on reproducing UI bugs and login-free onboarding states that occur without authentication.

What is the best way to debug logged-out onboarding issues in Warp?▼

The best way to debug logged-out onboarding issues is to use a specialized reproduction workflow that forces the Warp UI into an unauthenticated state, ensuring consistent issue tracking and accurate debugging.

Do I need to authenticate my account to reproduce UI issues in Warp?▼

No, you do not need to authenticate. This skill requires Warp to be used without authentication to accurately reproduce and track bugs specific to the logged-out UI experience.

Warp UI bug reproduction not working with active sessions, what are the limitations?▼

The limitation is that active authenticated sessions will prevent accurate reproduction. You must remain in a logged-out state without authentication to successfully replicate the reported UI bug.

Related Skills

Explore More Software Engineering Skills→
Luohao-YanLuohao-Yan
6

reproduce-bug-report-local

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

Community
Intermediate
buiducnhatbuiducnhat
52

fix

Diagnose software bugs through root-cause analysis and implement verified fixes.

Community
Intermediate
HeartcoolmanHeartcoolman
88

reproduce-bug-report-local

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

Community
Intermediate
Drock91Drock91

moonpay-feedback

Submit authenticated bug, feature, or general feedback from the MoonPay CLI.

Community
Basic