github-issue-triage

To triage GitHub issues in real time, this skill uses exhaustive pagination to fetch every issue within a time window, launching a dedicated background task per issue for strict isolation and streaming analysis results as they complete.

Automating GitHub issue triage with per-issue isolation is achieved by assigning one background task to each fetched issue, enabling parallel processing and real-time streaming of results before compiling a final comprehensive report.

Yes, streaming GitHub issue analysis results is supported by launching a dedicated background task per issue, which outputs findings in real time via background_output while operating on exhaustive pagination of the repository.

Fetching every GitHub issue within a specific time window is fully supported through exhaustive pagination, ensuring no issues are missed before each one is analyzed as a separate background task.

Generating a final comprehensive report after triaging GitHub issues happens automatically at the end of the run, compiling actionable insights from the real-time streamed results of each per-issue background task.

A key limitation when using background tasks to triage GitHub issues is that strict per-issue isolation requires launching a dedicated worker for every issue fetched, which may demand significant resources when processing repositories at scale.