dyad:feedback-to-issues

Converts customer feedback emails into deduplicated GitHub issues and drafts reply emails.

21.4k|2.6k|Updated Apr 11, 2025
One-click install
npx skills add https://github.com/dyad-sh/dyad --skill dyad-feedback-to-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dyad:feedback-to-issues
Source: https://github.com/dyad-sh/dyad/tree/main/.claude/skills/feedback-to-issues
Command: npx skills add https://github.com/dyad-sh/dyad --skill dyad-feedback-to-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Customer feedback arrives as unstructured emails or support tickets, making it hard to track individual requests, avoid duplicate bug reports, and respond to customers with concrete status updates.

Core Features & Use Cases

  • Feedback Parsing: Breaks raw feedback text into discrete, actionable issues with titles, types (bug, feature, improvement, question), and priority estimates.
  • Duplicate Detection: Searches existing GitHub issues via the gh CLI with multiple keyword variations to avoid filing duplicates.
  • Approval-Gated Issue Creation: Presents a report of already-filed and proposed new issues, then creates only approved issues with labels via gh issue create.
  • Reply Email Drafting: Generates a professional customer reply referencing each filed or existing issue URL.
  • Use Case: A maintainer receives a long customer email listing three bugs and two feature requests; the Skill extracts all five items, finds one already tracked, creates the other four after approval, and drafts a reply email with issue links.

Quick Start

Paste the customer feedback email text and ask the assistant to turn it into GitHub issues and draft a reply email.

Frequently Asked Questions about dyad:feedback-to-issues

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

FAQPage Schema
How do I turn customer feedback emails into GitHub issues?

Provide the feedback text or a file path as input. The Skill parses it into discrete issues with titles, types, and priorities, checks GitHub for duplicates, and creates approved issues using the gh CLI.

How to avoid creating duplicate GitHub issues from feedback?

The Skill searches existing open and closed issues with gh issue list using multiple keyword variations per item. Matches are reported as already filed, and only unmatched items are proposed as new issues.

Does this Skill create GitHub issues automatically without review?

No. It presents a report of already-filed and proposed new issues and waits for explicit user approval before running gh issue create. You can edit titles, priorities, or skip items first.

What input formats does the feedback parser accept?

It accepts raw feedback text such as an email body or support ticket passed as arguments, or a file path to a text file containing the feedback, which it reads and parses.

What are the limitations of automated feedback triage?

Duplicate detection depends on keyword search quality, so differently worded existing issues may be missed. Priority and type classification are estimates that should be reviewed during the approval step.