Description
Search GitHub issues and PRs assigned to you, needing triage, or matching custom queries
SKILL.md
Search GitHub Issues and PRs
Use gh CLI to search for issues and PRs beyond notifications. This covers your full "issues inbox" — assigned work, triage queue, open PRs, and custom queries.
My assigned issues
gh api /search/issues --jq '.items[] | {number, title, repo: .repository_url, state, labels: [.labels[].name], updated_at, html_url}' -f q='assignee:@me is:open is:issue sort:updated-desc'
My open PRs
gh api /search/issues --jq '.items[] | {number, title, repo: .repository_url, state, draft: .draft, updated_at, html_url}' -f q='author:@me is:open is:pr sort:updated-desc'
PRs waiting for my review
gh api /search/issues --jq '.items[] | {number, title, repo: .repository_url, state, updated_at, html_url}' -f q='review-requested:@me is:open is:pr sort:updated-desc'
Issues needing triage (no type label)
This depends on the repo's label conventions. Common pattern — issues with no bug, feature-request, or enhancement label:
gh api /search/issues --jq '.items[] | {number, title, labels: [.labels[].name], updated_at, html_url}' -f q='assignee:@me is:open is:issue -label:bug -label:feature-request -label:enhancement sort:updated-desc repo:{owner}/{repo}'
Replace {owner}/{repo} with the target repository.
Issues in a specific repo
gh api /search/issues --jq '.items[] | {number, title, state, labels: [.labels[].name], updated_at, html_url}' -f q='is:open is:issue repo:{owner}/{repo} sort:updated-desc'
Stale issues (no activity in 30 days)
gh api /search/issues --jq '.items[] | {number, title, updated_at, html_url}' -f q='assignee:@me is:open is:issue sort:updated-asc updated:<{30_days_ago_date}'
Replace {30_days_ago_date} with a date like 2026-01-24.
Issues by milestone
gh api /search/issues --jq '.items[] | {number, title, state, labels: [.labels[].name], html_url}' -f q='is:open milestone:"{milestone}" repo:{owner}/{repo}'
Custom query
The GitHub search syntax supports:
assignee:@me,author:@me,mentions:@meis:open,is:closed,is:issue,is:prlabel:bug,-label:duplicaterepo:owner/repo,org:microsoftreview-requested:@me,reviewed-by:@mesort:updated-desc,sort:created-descupdated:>2026-01-01(date filters)
gh api /search/issues --jq '.items[] | {number, title, state, labels: [.labels[].name], updated_at, html_url}' -f q='{query}'
Rules
- Run each search as a separate terminal invocation
- NEVER pipe to
jqor other programs — use--jq - NEVER add
2>/dev/nullor redirects
More skills from the vscode-team-kit repository
View all 14 skillscouncil-plan
perform multi-model council planning
May 13ArchitectureEngineeringMulti-AgentSystem Designcouncil-review
perform multi-model council code reviews
May 13Code ReviewEngineeringMulti-AgentPull Requestsfollow-goal
manage agent goals and stopping conditions
Jul 7AgentsMicrosoftProductivityinbox-add-reaction
add reactions to GitHub issues and PRs
Jul 7GitHubPull Requestsinbox-install-gh-cli
install GitHub CLI
May 13CLIGitHubinbox-mark-all-read
mark GitHub notifications as read
May 13GitHubProductivity
More from Microsoft
View publisherplaywright-trace
inspect Playwright trace files
playwright
Apr 6DebuggingPlaywrightTestingrushstack-best-practices
manage Rush monorepos with best practices
rushstack
Apr 6EngineeringLocal DevelopmentMicrosoftProject Management +1azure-ai-agents-persistent-dotnet
build AI agents with Azure .NET SDK
skills
Jul 3.NETAgentsAzureLLMazure-ai-anomalydetector-java
build anomaly detection applications with Java
skills
May 13AnalyticsAzureData AnalysisJava +2azure-ai-contentsafety-java
build content moderation applications with Azure AI
skills
Jul 7AI InfrastructureAzureJavaSecurityazure-ai-contentsafety-py
detect harmful content with Azure AI Content Safety
skills
Jul 18AzureComplianceLLMMicrosoft +2