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
- 3 months ago
- Last Updated
- 5 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
issue-prioritize
Fetch open issues from GitHub, GitLab, or Linear, score them by impact/urgency/readiness/risk, and recommend the top issues to address next. Analysis-only — no mutations.
next-issue
Surveys the current repo's open GitHub issues, ranks them by triage label and dependency graph, and recommends an optimal execution order; when you pick one to start, it gates on whether the issue is clear enough to execute and routes unclear ones to the grill-with-docs skill before any code is written. It can also render the board as a self-contained HTML map that groups issues into business lines, draws their dependency arrows, and spells out which feature each chain ships once completed. Use WHENEVER the user asks what to work on next, which issue to pick up, to list / prioritize / sequence the backlog, for a dependency analysis, to visualize / draw / map the issues, their relationships, business lines, or what completing a chain unlocks, anything about *their own* issues ("my issues", who's blocking me, who's waiting on me, "我负责的 / 分给我的 / 谁在阻塞我 / 谁在等我"), "下一个做什么 / 排一下 issue 优先级 / 接下来推进哪个 / 这个 issue 能直接做吗 / 把 issue 关系和业务线画出来 / 生成依赖图 / 看板", or is about to start an issue and needs to know if it's ready — eve
issue-pick
複数の open issue から「次に着手すべきもの」をユーザーと相談する read-only skill。各 issue を統一観点 (影響範囲 / 依存・blocker / 規模 / 緊急度) で整理し、推奨 1 件 + 補欠 1〜2 件を理由とともに提示する。state 変更や ranking の永続化はしない。