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 isdev_ghfor brevity in AI interactions.
Usage
dev_gh(action, query?, number?, format?, limit?, type?, state?, labels?, author?)Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
action | "search" | "context" | "related" | required | Action type |
query | string | ā | Search query (for search action) |
number | number | ā | Issue/PR number (for context/related) |
format | "compact" | "verbose" | "compact" | Output format |
limit | number | 10 | Maximum results |
type | "issue" | "pull_request" | all | Filter by type |
state | "open" | "closed" | "merged" | all | Filter by state |
labels | string[] | ā | Filter by labels |
author | string | ā | Filter by author |
Actions
Search
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 Related
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 indexto 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
}
}