New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Warp GUI Bug Reproduction

by warpdotdev in warpdotdev/warp

Warp-specific guidance for reproducing bugs in the logged-out desktop GUI, using the reporter's exact version and channel instead of building from source.

AGPL-3.0Auto-check passedTesting & QA

Install Warp GUI Bug Reproduction

skills CLI
$ npx skills add warpdotdev/warp --skill gui-reproduce-bug-report-local -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install warpdotdev/warp gui-reproduce-bug-report-local --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/gui-reproduce-bug-report-local .claude/skills/gui-reproduce-bug-report-local && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gui-reproduce-bug-report-local
GitHub stars
65k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
693 words
Files
1
Skills in repo
46
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Warp-specific guidance for reproducing bugs in the logged-out desktop GUI, using the reporter's exact version and channel instead of building from source.

  • Reproducing a reported Warp rendering or layout bug
  • SKILL.md covers Prerequisite: install the…, Scope, Warp version and install… and Logged-out Warp baseline, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Reproducing a bug against the exact version a reporter installed

What it does

This companion specializes the core `reproduce-bug-report` skill for Warp's GUI desktop front-end, and it applies only to bugs that can be shown while the app stays logged out. That covers visible interface bugs, interaction, rendering and layout issues, onboarding without login, settings, editor and terminal display problems. Reports that need an account, cloud sync, logged-in onboarding or login-only AI behavior are declared out of scope rather than handed to a repro agent.

For setup, the guidance prefers the exact Warp version and channel the reporter named and says not to build from source by default. The agent installs the matching Linux package or binary release instead. The headless TUI front-end is excluded and has its own skills for UI, testing and verification. The parent skill must be installed first, and the excerpt is cut off after the install strategy.

When your agent uses it

  • Reproducing a reported Warp rendering or layout bug
  • Reproducing a bug against the exact version a reporter installed
  • Deciding whether a bug report can be reproduced without logging in

Example prompts

  • “Reproduce this issue about a broken settings page using the version the reporter listed.”
  • “A user says the tab bar flickers on the stable channel. Try to reproduce it in the logged-out GUI.”
  • “Can this cloud-sync bug be reproduced with the logged-out workflow?”

Requirements

  • The parent reproduce-bug-report skill
  • A Linux environment where a Warp release package can be installed

What it can do on your machine

Read from SKILL.md and the folder at commit b113a6c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Warp GUI Bug Reproduction loads about 1.4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 693 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from warpdotdev/warp at commit b113a6c, republished under its AGPL-3.0 licence (© warpdotdev). 693 words, ~1,361 tokens.

Download SKILL.mdSave it as .claude/skills/gui-reproduce-bug-report-local/SKILL.md (or your agent's skills folder).
name
gui-reproduce-bug-report-local
description
GUI desktop app only. 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.
specializes
reproduce-bug-report
specializes_source
warpdotdev/common-skills:.agents/skills/reproduce-bug-report

Repo-specific bug reproduction guidance for warp

Scope — GUI desktop app only. This skill applies to Warp's GUI desktop front-end (the app/ crate on the WarpUI pixel/GPU framework). It does not apply to the headless TUI front-end (crates/warp_tui; cell-grid TuiElement library under crates/warpui_core/src/elements/tui), which has its own components, tests, and change-verification workflow. For TUI work, see the tui-ui-guidelines, tui-testing, and tui-verify-change skills instead.

Prerequisite: install the parent skill

This skill specializes the core reproduce-bug-report skill (named in the specializes frontmatter field) and is not functional on its own. Before applying its guidance, confirm the parent skill is installed and resolvable at .agents/skills/reproduce-bug-report/SKILL.md. If it is missing, install it first by copying the skill directory from the source declared in the specializes_source frontmatter field (warpdotdev/common-skills:.agents/skills/reproduce-bug-report). Then continue with the guidance below.

This 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.

Scope

  • Use this workflow only for Warp bugs that can be exercised while the app remains logged out.
  • Apply it to UI-visible Warp bugs, interaction bugs, rendering/layout bugs, logged-out onboarding bugs, settings bugs, editor/display bugs, terminal-display bugs, and other visual or interactive issues where screenshots or recordings would help.
  • Do not use it for authenticated-user flows, account-specific state, cloud-synced state, logged-in onboarding, or AI behaviors that require login.
  • If a report requires authentication, account state, cloud sync, or another logged-in-only capability, do not launch a repro agent with this local specialization; report that it is out of scope for the current logged-out Warp workflow.

Warp version and install strategy

  • Prefer reproducing against the exact Warp version/build and channel reported by the user.
  • Do not build Warp from source by default. Install the matching Linux package or binary release for the reporter's version/channel instead.
  • If the bug report names a macOS or Windows build, use the corresponding Linux build from the same version/channel when a matching Linux artifact exists, and state that this is a Linux proxy for the reporter's platform.
  • Use the repository's or Warp release tooling/docs available in the environment to find and install the exact versioned Linux artifact. Do not silently substitute the latest stable build when an exact matching version can be installed.
  • If the exact version/build cannot be found or installed, report that clearly, explain what was attempted, and use the closest justified fallback only when it is useful for continuing the investigation.
  • Record the requested reporter Warp version, the installed Linux version, the source of the installed artifact, and any fallback decision in the manifest and final report.
Show full SKILL.md (256 more words)Show less

Logged-out Warp baseline

  • Keep Warp logged out for the entire repro attempt. Do not create an account, sign in, paste auth tokens, or use real user credentials.
  • Launch Warp and complete the login-free / continue-without-account onboarding path until a normal logged-out terminal session is usable.
  • Capture a post-onboarding baseline screenshot before attempting the bug-specific reproduction.
  • If the assigned bug cannot be exercised after entering a normal logged-out Warp session, stop and report the blocker instead of improvising an authenticated flow.

Local prompt additions

When applying the core skill to Warp, ensure the parent prompt and child prompts include:

  • Reporter Warp version/build/channel: the exact value from the report, or unknown.
  • Build/app target: the exact versioned Linux Warp package/binary to install, or the justified fallback if an exact artifact is unavailable.
  • Assigned Warp state: first-run logged-out state, completed logged-out onboarding, terminal/session/layout/settings state, or the targeted code-path hypothesis.
  • A reminder that Warp must remain logged out and that logged-in-only reports are blocked for this specialization.

Local reproduction priorities

  • Match the reporter's Warp version/build/channel before broadening the search space.
  • Follow the issue's exact steps first, then test at most two targeted variations supported by the issue or by a code-path hypothesis.
  • Prefer targeted hypotheses derived from Warp UI strings, settings names, feature names, telemetry names, route names, and relevant components over broad exploratory clicking.
  • In the final report, include:
    • the reporter-requested Warp version/build/channel
    • the installed Linux Warp version/build/channel
    • the package or binary source
    • whether a fallback was used
    • whether the test was a Linux proxy for a macOS or Windows report

© warpdotdev, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/gui-reproduce-bug-report-local of warpdotdev/warp.

Open the folder on GitHubat commit b113a6c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in warpdotdev/warp, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Warp GUI Bug Reproduction next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Warp GUI Bug Reproduction compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Warp GUI Bug Reproduction this skillwarpdotdev/warp65k1 repos~1.4kAutomated safety check: PassAGPL-3.0
Dogfood Exploratory QAvercel-labs/agent-browser44k8 repos~2.7kAutomated safety check: PassApache-2.0
DeerFlow Smoke Testbytedance/deer-flow84k—~2.5kAutomated safety check: NotesMIT
CodexBar Live QAsteipete/CodexBar22k—~1.2kAutomated safety check: PassMIT
Diagnose Playwright Failure as Product Bugappsmithorg/appsmith41k—~1.5kAutomated safety check: PassApache-2.0
Acceptance Evidence for Deliverieslobehub/lobehub83k—~9.7kAutomated safety check: PassApache-2.0

Similar skills

  • Dogfood Exploratory QA

    vercel-labs/agent-browser

    Official

    Explores a web app with the agent-browser CLI to find bugs and UX problems, then writes a report with screenshots, repro videos and step-by-step reproduction for each issue.

    44k GitHub starsUsed in 8 repos~2.7k tokens
    Testing & QAAuto-check passed

  • DeerFlow Smoke Test

    bytedance/deer-flow

    Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.

    84k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check: notes

  • CodexBar Live QA

    steipete/CodexBar

    Runs live QA for the CodexBar app: provider usage matrix checks through its packaged CLI, config validation and menu checks, with 1Password-backed credentials handled safely.

    22k GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Diagnose Playwright Failure as Product Bug

    appsmithorg/appsmith

    Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.

    41k GitHub stars~1.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Acceptance Evidence for Deliveries

    lobehub/lobehub

    Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.

    83k GitHub stars~9.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Codex Plugin QA

    code-yeongyu/oh-my-openagent

    Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.

    70k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed

More from warpdotdev/warp

All 46 skills in this repo

  • Figma Design System Builder

    warpdotdev/warp

    Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Auto-check passed

  • Figma use_figma Plugin API Rules

    warpdotdev/warp

    Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Auto-check passed

  • Warp Factory Files

    warpdotdev/warp

    Authors and edits file-based Warp software factory definitions rooted at factory.yaml, covering agents, automations, scorers and webhooks, and validates them before a pull request.

    65k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Figma Design to Code

    warpdotdev/warp

    Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

    65k GitHub starsUsed in 4 repos~2.9k tokens
    Auto-check passed

  • Warp GUI to Agent CLI Migration

    warpdotdev/warp

    Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

  • Figma Design System Rules Generator

    warpdotdev/warp

    Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.

    65k GitHub starsUsed in 3 repos~4.6k tokens
    Auto-check passed

Categories

Questions about Warp GUI Bug Reproduction

What does Warp GUI Bug Reproduction do?

Warp-specific guidance for reproducing bugs in the logged-out desktop GUI, using the reporter's exact version and channel instead of building from source. This companion specializes the core `reproduce-bug-report` skill for Warp's GUI desktop front-end, and it applies only to bugs that can be shown while the app stays logged out. That covers visible interface bugs, interaction, rendering and layout issues, onboarding without login, settings, editor and terminal display problems.

When should I use Warp GUI Bug Reproduction?

Warp GUI Bug Reproduction fits situations like: reproducing a reported Warp rendering or layout bug; reproducing a bug against the exact version a reporter installed; deciding whether a bug report can be reproduced without logging in.

How do I install Warp GUI Bug Reproduction in Claude Code?

Run `npx skills add warpdotdev/warp --skill gui-reproduce-bug-report-local -a claude-code`. Or copy the skill folder (.agents/skills/gui-reproduce-bug-report-local in warpdotdev/warp) into .claude/skills/gui-reproduce-bug-report-local in your project. Claude Code loads it when a task matches its description.

How do I install Warp GUI Bug Reproduction in Codex?

Run `npx skills add warpdotdev/warp --skill gui-reproduce-bug-report-local -a codex`. Or copy the skill folder (.agents/skills/gui-reproduce-bug-report-local in warpdotdev/warp) into .agents/skills/gui-reproduce-bug-report-local in your project. Codex loads it when a task matches its description.

Can I use Warp GUI Bug Reproduction in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add warpdotdev/warp --skill gui-reproduce-bug-report-local -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gui-reproduce-bug-report-local, .gemini/skills/gui-reproduce-bug-report-local, .github/skills/gui-reproduce-bug-report-local and .opencode/skills/gui-reproduce-bug-report-local in your project.

What does Warp GUI Bug Reproduction need to run?

SKILL.md names no scripts, command-line tools or credentials: Warp GUI Bug Reproduction is instructions for the agent only. Our summary lists: The parent reproduce-bug-report skill; A Linux environment where a Warp release package can be installed.

Does Warp GUI Bug Reproduction access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Warp GUI Bug Reproduction safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Warp GUI Bug Reproduction use?

Warp GUI Bug Reproduction is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Warp GUI Bug Reproduction use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Warp GUI Bug Reproduction?

Skills that share tags, products or a category with Warp GUI Bug Reproduction: Dogfood Exploratory QA (vercel-labs/agent-browser, 44k stars), DeerFlow Smoke Test (bytedance/deer-flow, 84k stars), CodexBar Live QA (steipete/CodexBar, 22k stars) and Diagnose Playwright Failure as Product Bug (appsmithorg/appsmith, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Warp GUI Bug Reproduction?

warpdotdev (a GitHub organization) maintains it in warpdotdev/warp, which has 65,402 GitHub stars. The repository holds 46 skills in this directory. The repository was last updated on October 9, 2026.

Source: warpdotdev/warp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.