en un clic
github-scanning
Search GitHub for issues, PRs, discussions, releases, and alerts. Includes query construction, date range handling, repo scoping, and cross-repo intelligence.
Menu
Search GitHub for issues, PRs, discussions, releases, and alerts. Includes query construction, date range handling, repo scoping, and cross-repo intelligence.
Basé sur la classification professionnelle SOC
Use for web accessibility work in HTML, JSX, CSS, ARIA, keyboard, forms, contrast, modals, live regions, headings, links, tables, or WCAG review; starts accessibility-lead first and uses tool_search if subagent tools are lazy-loaded.
Developer tools accessibility router for Python, wxPython, desktop accessibility APIs, NVDA add-ons, scanner tooling, CI tooling, and accessibility developer experience.
Document accessibility router for Word, Excel, PowerPoint, PDF, EPUB, Office remediation, PDF remediation, and accessible generated documents.
GitHub workflow accessibility router for PR review, issues, Actions, releases, projects, security alerts, notifications, repository management, and accessible contributor workflows.
Markdown accessibility router for docs, README files, headings, links, tables, alt text, diagrams, generated docs, and publication-ready accessible markdown.
Compute web accessibility scores (0-100, A-F grades) with severity scoring, confidence levels, and remediation tracking across audits.
| name | github-scanning |
| description | Search GitHub for issues, PRs, discussions, releases, and alerts. Includes query construction, date range handling, repo scoping, and cross-repo intelligence. |
| Intent | Query Pattern | Scope |
|---|---|---|
| Assigned to you | is:open assignee:USERNAME | All repos |
| You were @mentioned | is:open mentions:USERNAME | All repos |
| Authored by you | is:open author:USERNAME | All repos |
| Specific repo | repo:owner/repo is:open | Single repo |
| By keyword | {keyword} is:open | All repos |
| Org-wide | org:ORGNAME is:open | Org repos |
| Closed (for recap) | is:closed author:USERNAME | All repos |
| Intent | Query Pattern | Scope |
|---|---|---|
| Awaiting your review | review-requested:USERNAME state:open | All repos |
| Your open PRs | author:USERNAME state:open | All repos |
| Assigned to you | assignee:USERNAME state:open | All repos |
| You reviewed, check for updates | reviewed-by:USERNAME state:open | All repos |
| Specific PR | Fetch directly with owner, repo, number | Single repo |
| Org-wide | org:ORGNAME state:open | Org repos |
| Intent | Action |
|---|---|
| You're mentioned | Search with mentions:USERNAME |
| You're participating | Search discussions you've commented on |
| High activity | Filter for 10+ comments in last 24h |
| Linked to your issues | Scan description/comments for issue references |
github_list_releases per repo - check for recent, draft, and pre-releases.dependabot[bot] or renovate[bot].Convert natural language to GitHub query qualifiers:
| User Says | GitHub Qualifier |
|---|---|
| "last week" | created:>YYYY-MM-DD (7 days ago) |
| "this month" | created:>YYYY-MM-01 |
| "today" | closed:YYYY-MM-DD |
| "this week" | closed:>YYYY-MM-DD (7 days ago) |
| "between X and Y" | created:X..Y |
| Not specified | Use search.default_window from preferences (default: updated:>YYYY-MM-DD 30 days) - mention this assumption |
| "for current month" (a11y tracker) | milestone:"{Month} {Year}" |
Add qualifiers to narrow by scope when the user specifies one:
| Scope | Qualifier |
|---|---|
| Single repo | repo:owner/name |
| All org repos | org:orgname |
| All repos by user | user:username |
| Everything (default) | No qualifier - searches all accessible repos |
Read .github/agents/preferences.md and apply these filters before and after searching:
repos.discovery - determines the default search scope (all / starred / owned / configured / workspace).repos.include - always include these repos even in restricted modes.repos.exclude - skip these repos in all searches.repos.overrides - per-repo settings:
track.issues: false -> skip issue searches for this repotrack.pull_requests: false -> skip PR searches for this repotrack.discussions: false -> skip discussions for this repotrack.releases: false -> skip release checks for this repotrack.security: false -> skip security alerts for this repotrack.ci: false -> skip CI status for this repolabels.include / labels.exclude -> filter results by labelpaths -> only trigger for changes touching these file paths (for PRs/CI)assignees -> filter to specific assignees (empty = all)search.default_window - default time range if the user doesn't specify one.briefing.sections - which sections to include in the daily briefing.accessibility_tracking - config for the a11y tracker (repos, labels, channels).When results arrive from different repos, look for and surface these patterns:
| Pattern | Action |
|---|---|
| Cross-repo references | When issue A contains owner/repo#N, fetch and surface item N |
| Shared label patterns | Group items in different repos tagged P0 together in triage |
| Related PRs in different repos | Flag: "This issue depends on PR #N in repo-B which is still open" |
| Merged PR not yet released | Note: "Your PR #N is merged but not in any release yet" |
| Issue with merged fix PR | Flag: "This may be resolved - PR #N that closes it was merged on {date}" |
| Branch naming patterns | Group PRs in different repos using the same branch naming convention |
For agents that collect from multiple data streams, run independent streams simultaneously. Don't serialize operations with no dependencies.
Batch 1 - fully independent, run simultaneously:
Batch 2 - run after Batch 1 (CI needs PR list from Batch 1):
Batch 3 - can overlap with Batch 2:
Batch 1 - collection (all independent):
Batch 2 - analysis (depends on Batch 1 data):
Running {N} searches in parallel... ({scope})
Batch 1 complete - {X} items found
Running {N} additional searches...
Batch 2 complete - {Y} items found
Scoring and prioritizing...
Done - {Z} items need action, {W} to monitor
If a search returns 0 results:
all, or remove label filters.Recovery cascade:
When the same item appears in multiple searches (e.g., an issue you're both assigned to AND mentioned in):