feedback

Convert user feedback into GitHub issues for the Warp app.

30|4|Updated May 3, 2026

Search Tags:#GitHub #issue management #duplicate detection #feedback analysis #issue filing

Ready to run

npx skills add https://github.com/OniroHuaver/openwarp --skill feedback-onirohuaver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/OniroHuaver/openwarp/tree/main/resources/bundled/skills/feedback
Command: npx skills add https://github.com/OniroHuaver/openwarp --skill feedback-onirohuaver

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill turns rough feedback into a clear GitHub issue or duplicate response for the Warp app, streamlining the process of issue triage and resolution.

Core Features & Use Cases

Issue Filing: Draft and file a GitHub issue with detailed information about user feedback.
Duplicate Detection: Check for existing issues with similar titles to avoid duplicate submissions.
Scope Verification: Verify whether the feedback is within the scope of the Warp product.
Feature Request Handling: Classify feedback as a feature request and guide the user on how to proceed.

Quick Start

Run the feedback skill to transform the user's feedback into a GitHub issue.

Frequently Asked Questions about feedback

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

FAQPage Schema

How do I automate GitHub issue creation from user feedback for the Warp app?▼

You can automate GitHub issue creation by running this Skill to transform rough user feedback into a structured Warp GitHub issue. It drafts the issue details, verifies the scope, and utilizes the gh CLI for code lookups and submission.

How does duplicate detection work when filing GitHub issues from feedback?▼

Duplicate detection works by checking for existing GitHub issues with similar titles to your user feedback. This prevents redundant submissions and ensures that new feedback is only filed as a unique issue on the Warp repository.

Do I need local Warp source code access to file feedback as a GitHub issue?▼

Yes, you need local Warp source code access and appropriate user permissions to file feedback as a GitHub issue. The Skill utilizes the gh CLI to perform code lookups and verify the scope of the feedback against the local source.

What is the best way to classify user feedback into bugs, regressions, or feature requests?▼

The best way to classify user feedback is to use this Skill, which automatically categorizes input as a bug, regression, UX issue, or feature request. It guides feature request handling and structures the classification for GitHub issue filing.

Can I use the gh CLI to check if user feedback is within the scope of the Warp product?▼

Yes, you can use this Skill with the gh CLI to check if user feedback is within the scope of the Warp product. It performs scope verification during the feedback analysis process before attempting to draft and file a GitHub issue.

What are the limitations of automating issue triage with the gh CLI for the Warp app?▼

Limitations of automating issue triage include requiring local Warp source code access and appropriate user permissions. Without these, the Skill cannot perform code lookups, scope verification, or draft and file the GitHub issue properly.