pick-next-issue

Featured

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".

Web & Frontend 402 stars 30 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
87
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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,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 fu...

Details

Author
tobihagemann
Repository
tobihagemann/turbo
Created
6 months ago
Last Updated
2 days ago
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

next

Triage open GitHub issues and recommend what to work on next. Builds a dependency graph from issue bodies, detects circular dependencies, ranks unblocked issues by weighted scoring (blocks-others, priority, type, age, milestone), and presents top candidates for interactive selection. Triggers: what should I work on next, triage backlog, next issue, pick next task, recommend issue, prioritize issues.

10 Updated 5 days ago
rube-de
Code & Development Listed

issues

List and rank the forge issues assigned to you so you can pick what to work on next — ranked by soonest due date, then most recently updated. Use whenever finding, browsing, surveying, or choosing the next issue/ticket to pick up, even when the user doesn't say "issues" — e.g. "what's next?", "what should I work on?", "anything due soon?", "show my open tickets". For filing or updating a single issue, use the `issue` skill instead.

0 Updated 4 days ago
chris-peterson
API & Backend Listed

pick-issue

Survey all open GitHub issues, pending Dependabot PRs, and human-authored pull requests, pick the single best next thing to work on, and hand it to the right builder skill. An open non-draft human PR is reviewed first — only a security exposure or broken core functionality outranks it; everything else is ranked by value-for-effort. Use when asked "what should I work on/implement next?", to triage the backlog, or to choose and start the next issue. Hands the winner to `implement` (issues), `dependabot` (dependency PRs), or `review-pr` (human PRs).

1 Updated today
ChulioZ