test-queue

This Skill identifies and surfaces testing issues from your GitHub project, sorts them by how long they've been waiting, and groups them by repository. It uses GitHub GraphQL to fetch issues marked as Testing, calculates wait time, and generates a markdown report highlighting which tests have been waiting longest so you can prioritize review.

Yes. The Skill applies across multi-repo environments to fetch all outstanding test-queue issues, groups them by repository, and presents per-issue details including number, title, creation date, repository name, and assignees in a single organized report.

It highlights issues waiting three or more days, marking long-waiting items for prioritization. By sorting all Testing-marked issues by elapsed time since creation and grouping by repository, you quickly spot bottlenecks and allocate QA resources to the oldest pending tests.

The markdown report surfaces issue number, title, creation timestamp, repository, and assigned reviewers. Issues are ordered by wait time within each repository group, so you see both what's waiting and how long it's been pending in one view.

Yes. The Skill uses GitHub GraphQL to query your projects, so you need authenticated access to the repositories you want to analyze. It pulls issues marked with the Testing label and retrieves metadata needed to calculate and display wait times.

Use this Skill to generate a standardized markdown report on demand or on schedule. By applying it across your multi-repo environment and surfacing long-waiting tests grouped by repository, teams get a consistent, data-driven view of QA bottlenecks without manual triage.