tobihagemann/turbo-pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to \"pick next issue\", \"next issue\", \"which issue should I work on\", \"top issues\", \"most popular issues\", \"prioritize issues\", or \"what should I work on next\".
npx skills add https://github.com/tobihagemann/turbo --skill pick-next-issue
Rank open GitHub issues by engagement and plan the selected issue.
Run gh issue list to fetch open issues with engagement data:
gh issue list --state open --json number,title,url,reactionGroups,comments,labels,createdAt --limit 50
Calculate an engagement score for each issue:
reactionGroups (thumbs up, heart, hooray, etc.). Weight thumbs-up (THUMBS_UP) reactions 2x since they signal explicit demand.(weighted reactions) + commentsSort issues by engagement score descending.
Present the top 3 issues in a numbered list. For each issue, show:
If fewer than 3 open issues exist, present all of them.
If no open issues exist, inform the user and stop.
Ask the user to pick one of the presented issues (or request to see more).
If the user asks to see more, present the next 3 issues from the ranked list.
Fetch the complete issue details for the selected issue:
gh issue view <number> --json number,title,body,url,labels,comments,reactionGroups,assignees,milestone
Read the full issue body and comments to understand the requirements and any discussion context.
$turboplan SkillRun the $turboplan skill with the issue body as the task description. Tell turboplan that the plan must include a final implementation step: "Close issue #N or reference it in the PR with Closes #N."
gh CLI authenticated with access to the current repogh fails (not in a repo, not authenticated), inform the user and stopTake tobihagemann/turbo-pick-next-issue from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.