القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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. |
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: The customer feedback text (email body, support ticket, etc.). Can also be a file path to a text file containing the feedback.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:
bug, feature, improvement, or questionhigh, medium, or lowIgnore 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:
For each issue that already has a matching GitHub issue, show:
For each issue that does NOT have an existing match, show:
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:
Present the draft email to the user for review before they send it.
Commit any uncommitted changes, run lint checks, fix any issues, and push the current branch.
Root-cause flaky or failing E2E tests from a specific CI run by downloading and analyzing the Playwright HTML report (traces, screenshots, errors). Use this when given a GitHub Actions run URL and asked to investigate failures. Diagnose from report artifacts first, then rebuild and rerun the affected E2E tests locally after making fixes.
Fix failing CI checks and GitHub Actions on a Pull Request.
Read all unresolved GitHub PR comments from trusted authors and address or resolve them appropriately.
Automatically gather flaky E2E tests from recent CI runs on the main branch and from recent PRs by wwwillchen/keppo-bot/dyad-assistant, then deflake them.
Promote the latest pre-release to a stable release by creating a release branch, bumping the version, and pushing.