agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/vscode-team-kit/github-inbox/skills/inbox-search-issues/SKILL.md

inbox-search-issues

Skill65 starsChanged 16 days agoMITView on GitHub

Search GitHub issues and PRs assigned to you, needing triage, or matching custom queries

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use gh CLI to search for issues and PRs beyond notifications.

    line 10
  2. Distinctive:

    Run each search as a separate terminal invocation

    line 77
  3. Very specific:

    NEVER pipe to jq or other programs — use --jq

    line 78
  4. Very specific:

    NEVER add 2>/dev/null or redirects

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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:@me
  • is:open, is:closed, is:issue, is:pr
  • label:bug, -label:duplicate
  • repo:owner/repo, org:microsoft
  • review-requested:@me, reviewed-by:@me
  • sort:updated-desc, sort:created-desc
  • updated:>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 jq or other programs — use --jq
  • NEVER add 2>/dev/null or redirects

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free