pick-next-issue
SolidFetch 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
Quality Score: 89/100
Skill Content
Details
- Author
- tobihagemann
- Repository
- tobihagemann/turbo
- Created
- 4 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
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.
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).
find-issues
Find open issues in ONE GitHub repository that fit the user's contribution profile. Use for "what can I contribute to <repo>" or good-first-issue hunting in a single repo.