Agent skill
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".
Install this agent skill to your Project
npx add-skill https://github.com/tobihagemann/turbo/tree/main/skills/pick-next-issue
SKILL.md
Pick Next Issue
Rank open GitHub issues by engagement and plan the selected issue.
Step 1: Fetch and Rank Issues
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:
- Reactions score: Sum all reaction counts from
reactionGroups(thumbs up, heart, hooray, etc.). Weight thumbs-up (THUMBS_UP) reactions 2x since they signal explicit demand. - Comments score: Count of comments on the issue.
- Engagement score:
(weighted reactions) + comments
Sort issues by engagement score descending.
Step 2: Present Top 3
Present the top 3 issues in a numbered list. For each issue, show:
- Title with issue number and link
- Labels (if any)
- Engagement: reaction breakdown and comment count
- Created: date
- First paragraph of the issue body (truncate if long)
If fewer than 3 open issues exist, present all of them.
If no open issues exist, inform the user and stop.
Step 3: User Picks an Issue
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.
Step 4: Read the Full Issue
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.
Step 5: Run /turboplan Skill
Run 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."
Rules
- Requires
ghCLI authenticated with access to the current repo - If
ghfails (not in a repo, not authenticated), inform the user and stop - Never modify issues. This skill is read-only until the implementation is committed.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
review-api-usage
Check API, library, and framework usage in code against official documentation and installed skill knowledge. Flags deprecated APIs, incorrect method signatures, wrong parameter types, version-incompatible patterns, and best-practice violations. Use when the user asks to "review API usage", "check API usage", "verify against docs", "check library usage", "validate API calls", "check against documentation", or "check for deprecated APIs".
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR feedback", "handle review comments", "address review feedback", "respond to PR comments", "answer review questions", or "address code review".
consult-codex
Multi-turn consultation with Codex CLI for second opinions, brainstorming, or collaborative problem-solving. Use when the user asks to "consult codex", "ask codex", "get codex's opinion", "brainstorm with codex", "discuss with codex", or "chat with codex".
review-tooling
Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what tooling is missing", "review dev infrastructure", or "tooling audit".
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
update-changelog
Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".
Didn't find tool you were looking for?