Skip to Content

dev_gh

Search GitHub issues and pull requests using semantic search. Understand your project’s history and context.

Note: The CLI command is dev github, but the MCP tool name is dev_gh for brevity in AI interactions.

Usage

dev_gh(action, query?, number?, format?, limit?, type?, state?, labels?, author?)

Parameters

ParameterTypeDefaultDescription
action"search" | "context" | "related"requiredAction type
querystring—Search query (for search action)
numbernumber—Issue/PR number (for context/related)
format"compact" | "verbose""compact"Output format
limitnumber10Maximum results
type"issue" | "pull_request"allFilter by type
state"open" | "closed" | "merged"allFilter by state
labelsstring[]—Filter by labels
authorstring—Filter by author

Actions

Semantic search across issues and PRs:

ā€œUse dev_gh action search, query ā€˜performance problems with large filesā€˜ā€œ

## GitHub Search Results Query: "performance problems with large files" 1. šŸ”“ #127: File upload times out for large files [92%] 2. 🟢 #98: Optimize chunked file processing [87%] 3. šŸ”µ PR #112: Add streaming for large file uploads [84%]

Get Context

Get full context for a specific issue or PR:

ā€œUse dev_gh action context, number 42ā€

## Issue #42: Add user preferences API **State:** Open | **Author:** @developer | **Labels:** enhancement, api ### Description We need an API endpoint for user preferences... ### Comments (3) 1. @reviewer: Should we use JSON or a dedicated table? 2. @developer: I'm thinking a separate preferences table... 3. @maintainer: Let's go with the table approach. ### Related PRs - PR #45: Database schema updates (merged)

Find issues/PRs related to a specific one:

ā€œUse dev_gh action related, number 42ā€

## Related to #42: Add user preferences API 1. #38: User settings page redesign [89%] 2. #29: API authentication improvements [76%] 3. PR #45: Database schema updates [72%]

Examples

Filter Open Bugs

ā€œUse dev_gh action search, query ā€˜crash’, type issue, state open, labels [ā€˜bug’]ā€œ

Find Author’s Issues

ā€œUse dev_gh action search, query ā€˜refactor’, author ā€˜usernameā€˜ā€œ

Requirements

āš ļø Index GitHub first. Run dev github index to enable semantic search:

dev github index

This fetches and indexes your repository’s issues and PRs.

Tips

Search by intent, not keywords. Try ā€œissues about slow API responsesā€ instead of ā€œperformanceā€.

GitHub index auto-reloads. Changes are detected automatically when you re-run dev github index.

Response Metadata

{ "metadata": { "tokens": 456, "duration_ms": 234, "results_total": 45, "results_returned": 10 } }
Last updated on