feedback

Convert Warp app feedback into GitHub issues with the in-app-feedback label.

37|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/terzigolu/warp-lite --skill feedback-terzigolu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/terzigolu/warp-lite/tree/main/resources/bundled/skills/feedback
Command: npx skills add https://github.com/terzigolu/warp-lite --skill feedback-terzigolu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn rough Warp app feedback into a crisp filed GitHub issue or duplicate-issue response for warpdotdev/warp.

Core Features & Use Cases

  • Use the gh CLI to search for and fetch code from warpdotdev/warp when product or implementation context would improve the report.
  • If those repos are not available, draft the issue from the user's report alone rather than blocking on more context.
  • This skill is strictly for issue filing and duplicate detection. Never modify code, generate patches, propose implementation diffs, or open a pull request as part of this workflow.
  • If you cannot file an issue, say so explicitly in the response instead of attempting another side effect.
  • The helper script applies the in-app-feedback label to filed issues for tracking.

Quick Start

Use the gh CLI to file a new Warp feedback issue with the in-app-feedback label.

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 a structured GitHub issue?

To turn rough Warp app feedback into a GitHub issue, this skill extracts reproduction steps, expected versus actual behavior, and grounded references, then drafts a crisp report for the warpdotdev/warp repository.

How do I file Warp bug reports using the gh CLI?

You can file Warp bug reports using the gh CLI by letting this skill draft the issue content and apply the in-app-feedback label automatically, ensuring the report is tracked correctly without manual repository edits.

Do I need the warpdotdev/warp repository available locally to draft feedback issues?

You do not need the warpdotdev/warp repository locally to draft feedback issues; if the repos are unavailable, the skill drafts the GitHub issue directly from your report alone rather than blocking on more context.

What is the best way to check for duplicate Warp issues before filing a new report?

The best way to check for duplicate Warp issues is using this skill's triage workflow, which searches existing reports in the warpdotdev/warp repository and generates a duplicate-issue response when a match is found.

Can this skill generate code patches or open pull requests for Warp feedback?

This skill cannot generate code patches or open pull requests; it is strictly for issue filing and duplicate detection, enforcing a safe workflow that never modifies code, proposes implementation diffs, or makes git changes.

How do I handle browser-based filing for Warp issues with attachments?

For Warp issues requiring attachments, this skill surfaces browser-based filing options instead of attempting another side effect, explicitly indicating when it cannot file an issue directly through the gh CLI.