Skill catalog: missing find-prs and find-issues skills
@SamMorrowDrums 已经在做这个了。
开始于 2026年6月10日。
评估
这个 Issue 还没有评估数据。
描述
Context
The github-mcp-server skill catalog exposes search_pull_requests and search_issues as raw tools, and bundles them inside higher-level skills like trace-history and prepare-release. There is no dedicated find-prs or find-issues skill — i.e. a small, focused skill whose contract is just "find PRs/issues matching these criteria, return a list".
Why this matters
Observed during an external evaluation harness (progressive-disclosure-evals) running model arms against the github-mcp-server skill catalog: when a task is "find recent PRs by author X" or "find issues mentioning Y", the model that browses the skill catalog reliably picks search_issues with type:pr qualifiers rather than search_pull_requests. Both go to the same /search/issues REST endpoint and are functionally equivalent, but the catalog lacks a discoverable "find-prs" entry point, so the model lands on the more generic search_issues path.
This is fine for correctness (it works) but it has two downstream effects:
- Evaluation rubrics that mention
search_pull_requestsas the expected tool now have to encode that-or-search_issuesequivalence themselves (we just shipped this as a schema change on our side). - Users / agents browsing the skill catalog see no obvious skill for the common "find PRs by author" workflow and have to either reach for
trace-history(which does more) or improvise withsearch_issues.
Ask
Consider adding two small skills:
find-prs— find pull requests matching author / repo / label / state / date / keyword criteria. Wrapssearch_pull_requests(orsearch_issues type:pr, doesn't matter which the implementation picks).find-issues— same shape for issues. Wrapssearch_issues type:issue.
These would be the obvious search-and-list entry points and would resolve the catalog-gap symptom described above.
Out of scope
I'm not asking you to change search_issues / search_pull_requests themselves, or to deprecate anything. This is purely about a discoverability gap in the higher-level skill layer.
- 主要语言
- Go
- 星标
- 33.1k
- 派生
- 5k
- 平均合并
- 2 天 1 小时
- 30 天内合并 PR
- 25
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
github/github-mcp-server 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
github/github-mcp-server#3235 ·
-
enhancement
难度 1/5 1 小时以内 新手友好度 88/100
github/github-mcp-server#3042 · 2 条评论 ·
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
github/github-mcp-server#3032 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 74/100
github/github-mcp-server#2803 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
github/github-mcp-server#2740 ·
查看 github/github-mcp-server 的全部 Issue
相似的 Issue
-
area/dev-productivity area/disaster-recovery area/ipcei kind/enhancement
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 1/5 1 小时以内 新手友好度 85/100
-
难度 2/5 1-3 小时 新手友好度 75/100
-
kind/bug status/0-triage
难度 2/5 1-3 小时 新手友好度 75/100
-
🤔 refinement needed
难度 2/5 1-3 小时 新手友好度 75/100
equinor/radix-operator#1979 ·