Files
Serendipity 1a1254f045
CI - 构建、测试和质量检查 / Rust 代码检查 (push) Has been cancelled
CI - 构建、测试和质量检查 / 单元测试 (push) Has been cancelled
CI - 构建、测试和质量检查 / 代码格式检查 (push) Has been cancelled
CI - 构建、测试和质量检查 / Clippy 代码质量检查 (push) Has been cancelled
CI - 构建、测试和质量检查 / 构建可执行文件 (claude_code_rs, macos-latest, x86_64-apple-darwin) (push) Has been cancelled
CI - 构建、测试和质量检查 / 构建可执行文件 (claude_code_rs, ubuntu-latest, x86_64-unknown-linux-gnu) (push) Has been cancelled
CI - 构建、测试和质量检查 / 构建可执行文件 (claude_code_rs.exe, windows-latest, x86_64-pc-windows-msvc) (push) Has been cancelled
feat: 添加初始项目结构和基础文件
- 添加 Rust GUI 桌面应用程序入口点
- 添加 TypeScript/JavaScript 项目基础结构文件
- 包含组件、工具、命令、服务和工具定义
- 添加配置文件如 .gitignore、.gitattributes 和 LICENSE
- 包含图片资源和演示文件
- 为各种功能模块添加占位符和类型定义
2026-04-20 16:58:22 +08:00

1.7 KiB

allowed-tools, description
allowed-tools description
Bash(./scripts/gh.sh:*), Bash(./scripts/comment-on-duplicates.sh:*) Find duplicate GitHub issues

Find up to 3 likely duplicate issues for a given GitHub issue.

To do this, follow these steps precisely:

  1. Use an agent to check if the Github issue (a) is closed, (b) does not need to be deduped (eg. because it is broad product feedback without a specific solution, or positive feedback), or (c) already has a duplicates comment that you made earlier. If so, do not proceed.
  2. Use an agent to view a Github issue, and ask the agent to return a summary of the issue
  3. Then, launch 5 parallel agents to search Github for duplicates of this issue, using diverse keywords and search approaches, using the summary from #1
  4. Next, feed the results from #1 and #2 into another agent, so that it can filter out false positives, that are likely not actually duplicates of the original issue. If there are no duplicates remaining, do not proceed.
  5. Finally, use the comment script to post duplicates:
    ./scripts/comment-on-duplicates.sh --potential-duplicates <dup1> <dup2> <dup3>
    

Notes (be sure to tell this to your agents, too):

  • Use ./scripts/gh.sh to interact with Github, rather than web fetch or raw gh. Examples:
    • ./scripts/gh.sh issue view 123 — view an issue
    • ./scripts/gh.sh issue view 123 --comments — view with comments
    • ./scripts/gh.sh issue list --state open --limit 20 — list issues
    • ./scripts/gh.sh search issues "query" --limit 10 — search for issues
  • Do not use other tools, beyond ./scripts/gh.sh and the comment script (eg. don't use other MCP servers, file edit, etc.)
  • Make a todo list first