Reviews open GitHub issues in the current repo, applies priority labels, checks relevance, and recommends the next issues to work on. Use when the user mentions prioritising issues, triaging the backlog, "what should I work on next", ranking issues, labelling priorities, or reviewing open issues for importance.
How this skill is triggered — by the user, by Claude, or both
Slash command
/issue-prioritiser-plugin:issue-prioritiserThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review open issues in the current repo, apply priority labels, assess relevance, and recommend the top issues to work on next.
Review open issues in the current repo, apply priority labels, assess relevance, and recommend the top issues to work on next.
closing-issues skill for that).Copy this checklist and keep it updated while working:
Issue Prioritisation Progress
- [ ] Step 1: Determine scope (repo, filter, label set)
- [ ] Step 2: Fetch matching issues
- [ ] Step 3: Assess and label each issue
- [ ] Step 4: Rank top recommendations
- [ ] Step 5: Report summary
Ask the user (if not already provided):
is:issue state:open (all open issues in the current repo).priority: highest, priority: high, priority: medium, priority: low, priority: nice to have.List all issues matching the filter. Note each issue's number, title, current labels, and age.
For each issue, evaluate three things:
A. Relevance — Is this still needed?
| Signal | Verdict |
|---|---|
| Feature/fix is already in the codebase | Flag as potentially done |
| Requirement is obsolete (superseded, no longer applies) | Flag as potentially stale |
| Still clearly needed | Relevant |
B. Clarity — Is the issue well-defined enough to act on?
If the description is vague, missing acceptance criteria, or ambiguous, post a comment asking for clarification. Don't guess at priority for unclear issues — label them priority: medium as a placeholder and note the question in the summary.
C. Priority — Apply a label based on:
| Factor | Raises priority | Lowers priority |
|---|---|---|
| User-facing impact | Blocks users, data loss, broken core flow | Cosmetic, edge case, nice-to-have |
| Frequency | Affects many/all users | Affects rare scenarios |
| Dependencies | Unblocks other issues | Standalone |
| Complexity vs value | High value, low effort | High effort, low value |
| Urgency | Security, compliance, outage | No deadline |
Apply exactly one priority label to each issue.
From the labelled issues, pick the top N (default 5) to recommend working on next. Order by priority label first, then by effort-to-value ratio. Briefly explain why each is recommended.
Issues reviewed: X
Labels applied: Y
Priority breakdown:
highest: N
high: N
medium: N
low: N
nice to have: N
Flagged for review:
- #12 — [title] — Possibly already done
- #34 — [title] — Needs clarification (question posted)
Recommended next 5:
1. #56 — [title] — [reason]
2. #78 — [title] — [reason]
3. #90 — [title] — [reason]
4. #11 — [title] — [reason]
5. #22 — [title] — [reason]
npx claudepluginhub awojtas/aidans-agent-skillsTriages GitHub issues assigned to you: fetches via GH CLI with cc-triage-scope label, builds dependency graph, categorizes resolved issues, and applies labels (cc-create-issue, cc-exec-issue, cc-update-issue).
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.