Token导航 LogoToken导航TokenDH.com
中转站排行榜
研究检索只读github未标认证来源可访问许可证需确认审计未展示

dyad%3afeedback-to-issues（成对%3a 反馈问题）

Agent Skill

用于围绕 GitHub 仓库、Issue、Pull Request、分支、提交和代码协作流程提供辅助能力。它适合让 Agent 查询项目状态、整理变更、辅助创建或检查协作事项，并把仓库中的信息转成可执行的下一步。使用时需要区分只读查询和写入操作；涉及创建 PR、修改 Issue、推送分支或访问私有仓库时，应确认 token 权限、目标仓库范围和用户授权。

总安装

612

周安装

25

GitHub Stars

20,189

下载量

196
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：dyad%3afeedback-to-issues（成对%3a 反馈问题）
来源仓库：https://github.com/dyad-sh/dyad
仓库路径：skills/dyad%3Afeedback-to-issues
安装命令：
npx skills add https://github.com/dyad-sh/dyad --skill dyad:feedback-to-issues
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

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

简介

从反馈中提取的问题总数：N

  • 已提交：N
  • 要创建的新问题：N
  • 然后要求用户查看并批准该提案，然后再继续。暂时不要创建任何问题。等待明确批准。用户可能想要编辑标题、描述、优先级或跳过某些问题。
  • 创建批准的问题：
  • 用户批准后（他们可以首先请求修改 - 应用这些修改），创建每个批准的问题：
  • gh问题创建--title“<标题>”--body“<body>”--label“<标签>”
  • 报告每个创建的问题及其编号和 URL。
  • 起草回复电子邮件：
  • 创建所有问题后，为客户起草一封简短、专业的回复电子邮件。电子邮件应：
  • 感谢他们的反馈
  • 简要确认他们提出的每一项
  • 对于已经存在问题的项目：提及它已被跟踪
  • 对于新创建的问题：提及已提交并将进行调查
  • 保持简洁——不超过几个简短的段落
  • 使用友好但专业的语气
  • 包含每个项目的 GitHub 问题 URL 链接，以便客户可以跟踪进度
  • 最后邀请您随时分享更多反馈
  • 在发送之前，将草稿电子邮件呈现给用户以供审阅。
  • 每周安装量
  • 25
  • 存储库
  • 二元组/二元组
  • GitHub 之星
  • 20.2K
  • 第一次看到
  • 5天前

SKILL.md

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

  1. 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: Ignore pleasantries, greetings, and non-actionable commentary. Focus on extracting concrete problems, requests, and suggestions.

- 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

  1. 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.
  2. 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: Proposed New Issues For each issue that does NOT have an existing match, show: Summary 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.

- The extracted issue title - The matching GitHub issue(s) with number, title, state (open/closed), and URL - Brief explanation of why it matches - 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 - Total issues extracted from feedback: N - Already filed: N - New issues to create: N

  1. 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.
  2. 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.

- 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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.28%
按下载量换算73

Claude

32.21%
按下载量换算63

Cursor

17.31%
按下载量换算34

Gemini CLI

9.08%
按下载量换算18

安全审计

暂无安全审计结果可展示。

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容，本身偏只读；真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/dyad-sh/dyad

SKILL.md 来源

github.com

/dyad-sh/dyad/tree/main/skills/dyad%3Afeedback-to-issues

skills-sh

skills.sh

/dyad-sh/dyad/dyad%3Afeedback-to-issues

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

dyad%3afast-push（成对%3a 快速推送）

dyad%3afast-push 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

dyad%3afix-issue（dyad%3a 修复问题）

用于围绕 GitHub 仓库、Issue、Pull Request、分支、提交和代码协作流程提供辅助能力。它适合让 Agent 查询项目状态、整理变更、辅助创建或检查协作事项，并把仓库中的信息转成可执行的下一步。使用时需要区分只读查询和写入操作；涉及创建 PR、修改 Issue、推送分支或访问私有仓库时，应确认 token 权限、目标仓库范围和用户授权。