tobihagemann/turbo / claude/skills/pick-next-issue
pick-next-issue
VerifiedRank open GitHub issues by engagement, present the top 3, and plan the selected one. Use when the user asks to "pick next issue", "which issue should I work on", or "what should I work on next".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.3 KB |
SKILL.md
View on GitHub---
name: pick-next-issue
description: "Rank open GitHub issues by engagement, present the top 3, and plan the selected one. Use when the user asks to \"pick next issue\", \"which issue should I work on\", or \"what should I work on next\"."
---
# 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:
```bash
gh issue list --state open --json number,title,body,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:
1. **Title** with issue number and link
2. **Labels** (if any)
3. **Engagement**: reaction breakdown and comment count
4. **Created**: date
5. **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:
```bash
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 `/plan` Skill
Run the `/plan` skill with the issue body as the task description. Tell `/plan` that the plan must include a final implementation step: "Close issue #N or reference it in the PR with `Closes #N`."
## Rules
- Requires `gh` CLI authenticated with access to the current repo
- If `gh` fails (not in a repo, not authenticated), inform the user and stop
- Never modify issues. This skill is read-only until the implementation is committed.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |