dyadfeedback-to-issues

Turn customer feedback (usually an email) into discrete GitHub issues. Checks for duplicates, proposes new issues for approval, creates them, and drafts a reply email.

Zur Installation springen

Repository: dyad-sh/dyad
Letzte Quellaktivität: 12. Februar 2026 um 21:05
Erkannte Sprache von SKILL.md: Englisch
Sterne: 21.222
Forks: 2.582

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/dyad-sh/dyad --skill dyadfeedback-to-issues

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

Zurück zur Suche Zurück zur Installation

dyad-pr-fix-ci

Diagnose and fix failing CI checks on a pull request from its latest GitHub Actions CI run. Use when PR CI has E2E/Playwright failures, macOS or Windows unit-test failures, or presubmit/type/build failures; analyzes the exact run logs and artifacts, invokes dyad:deflake-e2e-from-run for E2E failures, reproduces targeted unit tests locally, and publishes the fixes.

2026-07-22

dyad-pr-fix

Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks.

2026-07-22

dyad-pr-fix-comments

Read all unresolved GitHub PR comments from trusted authors and address or resolve them appropriately.

2026-07-21

Alle aus diesem Repository ansehen

Feedback to Issues

Turn customer feedback (usually an email) into discrete GitHub issues. Checks for duplicates, proposes new issues for approval, creates them, and drafts a reply email.

Arguments

$ARGUMENTS: The customer feedback text (email body, support ticket, etc.). Can also be a file path to a text file containing the feedback.

Instructions

Parse the feedback:

Read $ARGUMENTS carefully. If it looks like a file path, read the file contents.

Break the feedback down into discrete, actionable issues. For each issue, identify:

A concise title (imperative form, e.g., "Add dark mode support")
The type: bug, feature, improvement, or question
A clear description of what the customer is reporting or requesting
Severity/priority estimate: high, medium, or low
Any relevant quotes from the original feedback

Ignore pleasantries, greetings, and non-actionable commentary. Focus on extracting concrete problems, requests, and suggestions.

Search for existing issues:

For each discrete issue identified, search GitHub for existing issues that may already cover it:

gh issue list --repo "$(gh repo view --json nameWithOwner -q '.nameWithOwner')" --state all --search "<relevant keywords>" --limit 10 --json number,title,state,url

Try multiple keyword variations for each issue to avoid missing duplicates. Search both open and closed issues.

Present the report to the user:

Format the report in three sections:

Already Filed Issues

For each issue that already has a matching GitHub issue, show:

The extracted issue title
The matching GitHub issue(s) with number, title, state (open/closed), and URL
Brief explanation of why it matches

Proposed New Issues

For each issue that does NOT have an existing match, show:

Title: The proposed issue title
Type: bug / feature / improvement / question
Priority: high / medium / low
Body preview: The proposed issue body (include the relevant customer quote and a clear description of what needs to happen)
Labels: Suggest appropriate labels based on the issue type

Summary

Total issues extracted from feedback: N
Already filed: N
New issues to create: N

Then ask the user to review and approve the proposal before proceeding. Do NOT create any issues yet. Wait for explicit approval. The user may want to edit titles, descriptions, priorities, or skip certain issues.

Create approved issues:

After the user approves (they may request modifications first — apply those), create each approved issue:

gh issue create --title "<title>" --body "<body>" --label "<labels>"

Report back each created issue with its number and URL.

Draft a reply email:

After all issues are created, draft a brief, professional reply email for the customer. The email should:

Thank them for their feedback
Briefly acknowledge each item they raised
For items that already had existing issues: mention it's already being tracked
For newly created issues: mention it's been filed and will be looked into
Keep it concise — no more than a few short paragraphs
Use a friendly but professional tone
Include a link to the GitHub issue URL for each item so the customer can follow progress
End with an invitation to share more feedback anytime

Present the draft email to the user for review before they send it.

Feedback to Issues

Turn customer feedback (usually an email) into discrete GitHub issues. Checks for duplicates, proposes new issues for approval, creates them, and drafts a reply email.

Arguments

$ARGUMENTS: The customer feedback text (email body, support ticket, etc.). Can also be a file path to a text file containing the feedback.

Instructions

Parse the feedback:

Read $ARGUMENTS carefully. If it looks like a file path, read the file contents.

Break the feedback down into discrete, actionable issues. For each issue, identify:

A concise title (imperative form, e.g., "Add dark mode support")
The type: bug, feature, improvement, or question
A clear description of what the customer is reporting or requesting
Severity/priority estimate: high, medium, or low
Any relevant quotes from the original feedback

Ignore pleasantries, greetings, and non-actionable commentary. Focus on extracting concrete problems, requests, and suggestions.

Search for existing issues:

For each discrete issue identified, search GitHub for existing issues that may already cover it:

gh issue list --repo "$(gh repo view --json nameWithOwner -q '.nameWithOwner')" --state all --search "<relevant keywords>" --limit 10 --json number,title,state,url

Try multiple keyword variations for each issue to avoid missing duplicates. Search both open and closed issues.

Present the report to the user:

Format the report in three sections:

Already Filed Issues

For each issue that already has a matching GitHub issue, show:

The extracted issue title
The matching GitHub issue(s) with number, title, state (open/closed), and URL
Brief explanation of why it matches

Proposed New Issues

For each issue that does NOT have an existing match, show:

Title: The proposed issue title
Type: bug / feature / improvement / question
Priority: high / medium / low
Body preview: The proposed issue body (include the relevant customer quote and a clear description of what needs to happen)
Labels: Suggest appropriate labels based on the issue type

Summary

Total issues extracted from feedback: N
Already filed: N
New issues to create: N

Create approved issues:

After the user approves (they may request modifications first — apply those), create each approved issue:

gh issue create --title "<title>" --body "<body>" --label "<labels>"

Report back each created issue with its number and URL.

Draft a reply email:

After all issues are created, draft a brief, professional reply email for the customer. The email should:

Thank them for their feedback
Briefly acknowledge each item they raised
For items that already had existing issues: mention it's already being tracked
For newly created issues: mention it's been filed and will be looked into
Keep it concise — no more than a few short paragraphs
Use a friendly but professional tone
Include a link to the GitHub issue URL for each item so the customer can follow progress
End with an invitation to share more feedback anytime

Present the draft email to the user for review before they send it.

name	dyad:feedback-to-issues
description	Turn customer feedback (usually an email) into discrete GitHub issues. Checks for duplicates, proposes new issues for approval, creates them, and drafts a reply email.

dyadfeedback-to-issues

Quellinformationen

Installationsoptionen

Quelldateien prüfen

Mehr aus diesem Repository

Feedback to Issues

Arguments

Instructions

Already Filed Issues

Proposed New Issues

Summary

Mehr aus diesem Repository

Feedback to Issues

Arguments

Instructions

Already Filed Issues

Proposed New Issues

Summary