
Suggest Next Issue
- 2 repo stars
- Updated July 24, 2026
- cboone/agent-harness-plugins
Review open GitHub issues and recommend what to work on next, with prioritized reasoning.
About
Suggest-next-issue reviews open GitHub issues and recommends what to work on next, with prioritized reasoning behind each suggestion. It helps developers cut through a noisy backlog and pick the highest-value task. Aimed at devs and teams planning their next move.
- Reviews open issues
- Prioritized recommendation
- Reasoning included
- Triage and planning
Suggest Next Issue by the numbers
- Data as of Jul 25, 2026 (Skillselion catalog sync)
/plugin marketplace add cboone/agent-harness-plugins/plugin install suggest-next-issue@agent-harness-pluginsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | July 24, 2026 |
| Repository | cboone/agent-harness-plugins ↗ |
What it does
Review open GitHub issues and recommend what to work on next, with prioritized reasoning.
README.md
Suggest Next Issue
Review all open GitHub issues and recommend what to work on next with prioritized reasoning.
Type: Skill
Trigger: /suggest-next-issue
Requires: gh
Installation
See the marketplace install instructions.
What It Does
Analyzes open issues in context (current branches, issue labels, assignments, recent work, project goals, and dependencies), excludes issues already marked in progress, then categorizes the remaining candidates as quick wins, high impact, unblocks others, or overdue. Provides specific reasoning for each recommendation so you can make an informed decision.
Usage
/suggest-next-issue
Recommended Permissions
This skill runs GitHub CLI and git commands that trigger permission prompts. To allow them automatically, add these rules to your .claude/settings.json (project-wide) or ~/.claude/settings.json (global):
{
"permissions": {
"allow": ["Bash(gh issue list *)", "Bash(gh api *)", "Bash(gh repo view *)", "Bash(gh pr list *)", "Bash(git worktree list*)", "Bash(git branch *)"]
}
}
If you already have a permissions.allow array, merge these entries into it. Review and adjust the rules to match your security preferences.
Examples
- "suggest next issue": analyzes all open issues and recommends priorities
- "what should I work on next": same behavior
- "triage issues": same behavior
See Also
- Create Worktree from Issue: start working on the suggested issue
- All plugins