Skill catalog: missing find-prs and find-issues skills

Offen

#2,647 erstellt am 08.6.2026 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@SamMorrowDrums arbeitet bereits daran.

Seit 10.6.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

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_requests as the expected tool now have to encode that-or-search_issues equivalence 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 with search_issues.

Ask

Consider adding two small skills:

find-prs — find pull requests matching author / repo / label / state / date / keyword criteria. Wraps search_pull_requests (or search_issues type:pr, doesn't matter which the implementation picks).
find-issues — same shape for issues. Wraps search_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.

Vorherrschende Sprache: Go
Sterne: 33.1k
Forks: 5k
Ø Merge: 2 T. 1 Std.
Gemergte PRs (30 T.): 25

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/github-mcp-server

pull_request_read drops merge_commit_sha Offen

bug

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100

github/github-mcp-server#3235 · Erstellt am 07.9.2026
Add guidance on GitHub autolinked reference formatting for AI agents Offen

enhancement

Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100

github/github-mcp-server#3042 · 2 Kommentare · Erstellt am 08.8.2026
Incorrect install documentation leads to error "error: unknown option '-e'" Offen

bug

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100

github/github-mcp-server#3032 · 1 Reaktion · Erstellt am 06.8.2026
Document Kubernetes installation with the HelmForge Helm chart Offen

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100

github/github-mcp-server#2803 · 1 Kommentar · Erstellt am 01.7.2026
get_discussion and get_discussion_comments accept calls with missing required parameters instead of returning a validation error Offen

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100

github/github-mcp-server#2740 · Erstellt am 21.6.2026

Alle Issues in github/github-mcp-server