feedback

Convert rough Warp app feedback into GitHub issues with duplicate detection.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/89jobrien/warpx --skill feedback-89jobrien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/89jobrien/warpx/tree/main/resources/bundled/skills/feedback
Command: npx skills add https://github.com/89jobrien/warpx --skill feedback-89jobrien

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Turn rough Warp app feedback into a filed GitHub issue or a duplicate-issue response for warpdotdev/warp, enabling clear triage and reliable follow-through.

Core Features & Use Cases

  • Structure bug reports, UX notes, feature gaps, and short complaints into reproducible issues with reproduction steps, expected vs actual behavior, and grounded references from local Warp repos when available.
  • Determine the correct destination repository, file the issue via the gh CLI when possible, or use a browser-based flow for attachments,surfacing a ready-to-copy body if it is too long for the URL.
  • Strictly read-only context: never modify source files and never create patches as part of this workflow.

Quick Start

File a rough Warp feedback snippet to create a tracked issue in warpdotdev/warp.

Frequently Asked Questions about feedback

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

FAQPage Schema
How do I turn rough Warp app feedback into GitHub issues?▼

To turn rough Warp app feedback into GitHub issues, provide your raw user reports to be structured into actionable warpdotdev/warp issues with reproduction steps, expected vs actual behavior, and grounded local repository references.

Can I check if a Warp bug report is a duplicate of an existing GitHub issue?▼

Yes, you can check if a Warp bug report is a duplicate by mapping user feedback against existing GitHub issues in the warpdotdev/warp repository to identify matches and generate a duplicate-issue response.

Does the Warp feedback triage process require the gh CLI?▼

The Warp feedback triage process uses the gh CLI to file issues by default, but it can fall back to a browser-based flow for attachments and surface long issue bodies for manual pasting if needed.

What types of Warp app feedback can be structured into reproducible GitHub issues?▼

Bug reports, UX notes, feature gaps, and short complaints can be structured into reproducible GitHub issues, automatically formatting the Warp feedback with clear reproduction steps and expected behavior.

How do I file GitHub issues with attachments from Warp user reports?▼

To file GitHub issues with attachments from Warp user reports, the workflow falls back to a browser-based flow, surfacing a ready-to-copy issue body if the text is too long for the standard gh CLI URL submission.

Will converting Warp feedback to GitHub issues modify my local source files?▼

No, converting Warp feedback to GitHub issues operates strictly in a read-only context, meaning it will never modify your local source files or create patches as part of the triage workflow.