pick-next-issue

Name: pick-next-issue
Author: tobihagemann

3installs29forks

How to install pick-next-issue?

tobihagemann/turbo/pick-next-issue

$npx -y skills add tobihagemann/turbo --skill pick-next-issue

Installs into the current project.

Summary

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\", \"pri

Files · 1

View on GitHub

SKILL.md

1	# Pick Next Issue
2
3	Rank open GitHub issues by engagement and plan the selected issue.
4
5	## Step 1: Fetch and Rank Issues
6
7	Run `gh issue list` to fetch open issues with engagement data:
8
9	```bash
10	gh issue list --state open --json number,title,url,reactionGroups,comments,labels,createdAt --limit 50
11	```
12
13	Calculate an engagement score for each issue:
14
15	- 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.
16	- Comments score: Count of comments on the issue.
17	- Engagement score: `(weighted reactions) + comments`
18
19	Sort issues by engagement score descending.
20
21	## Step 2: Present Top 3
22
23	Present the top 3 issues in a numbered list. For each issue, show:
24
25	1. Title with issue number and link
26	2. Labels (if any)
27	3. Engagement: reaction breakdown and comment count
28	4. Created: date
29	5. First paragraph of the issue body (truncate if long)
30
31	If fewer than 3 open issues exist, present all of them.
32
33	If no open issues exist, inform the user and stop.
34
35	## Step 3: User Picks an Issue
36
37	Ask the user to pick one of the presented issues (or request to see more).
38
39	If the user asks to see more, present the next 3 issues from the ranked list.
40
41	## Step 4: Read the Full Issue
42
43	Fetch the complete issue details for the selected issue:
44
45	```bash
46	gh issue view <number> --json number,title,body,url,labels,comments,reactionGroups,assignees,milestone
47	```
48
49	Read the full issue body and comments to understand the requirements and any discussion context.
50
51	## Step 5: Run `/turboplan` Skill
52
53	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`."
54
55	## Rules
56
57	- Requires `gh` CLI authenticated with access to the current repo
58	- If `gh` fails (not in a repo, not authenticated), inform the user and stop
59	- Never modify issues. This skill is read-only until the implementation is committed.

People who liked this also viewed

6 picks

Type

pick-next-issue

3installs29forks

View on GitHub

How to install pick-next-issue?

tobihagemann/turbo/pick-next-issue

$npx -y skills add tobihagemann/turbo --skill pick-next-issue

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Pick Next Issue
2
3	Rank open GitHub issues by engagement and plan the selected issue.
4
5	## Step 1: Fetch and Rank Issues
6
7	Run `gh issue list` to fetch open issues with engagement data:
8
9	```bash
10	gh issue list --state open --json number,title,url,reactionGroups,comments,labels,createdAt --limit 50
11	```
12
13	Calculate an engagement score for each issue:
14
15	- 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.
16	- Comments score: Count of comments on the issue.
17	- Engagement score: `(weighted reactions) + comments`
18
19	Sort issues by engagement score descending.
20
21	## Step 2: Present Top 3
22
23	Present the top 3 issues in a numbered list. For each issue, show:
24
25	1. Title with issue number and link
26	2. Labels (if any)
27	3. Engagement: reaction breakdown and comment count
28	4. Created: date
29	5. First paragraph of the issue body (truncate if long)
30
31	If fewer than 3 open issues exist, present all of them.
32
33	If no open issues exist, inform the user and stop.
34
35	## Step 3: User Picks an Issue
36
37	Ask the user to pick one of the presented issues (or request to see more).
38
39	If the user asks to see more, present the next 3 issues from the ranked list.
40
41	## Step 4: Read the Full Issue
42
43	Fetch the complete issue details for the selected issue:
44
45	```bash
46	gh issue view <number> --json number,title,body,url,labels,comments,reactionGroups,assignees,milestone
47	```
48
49	Read the full issue body and comments to understand the requirements and any discussion context.
50
51	## Step 5: Run `/turboplan` Skill
52
53	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`."
54
55	## Rules
56
57	- Requires `gh` CLI authenticated with access to the current repo
58	- If `gh` fails (not in a repo, not authenticated), inform the user and stop
59	- Never modify issues. This skill is read-only until the implementation is committed.

People who liked this also viewed

6 picks

Type