メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/dyad-sh/dyad --skill dyadfeedback-to-issuesコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
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.