domains / families / software-engineering / issue-prioritizer

issue-prioritizer

separate

Prioritize GitHub issues by ROI, solution sanity, and architectural impact. Use when triaging or ranking issues to identify quick wins, over-engineered proposals, and actionable bugs. Don't use when managing forks (use fork-manager) or general GitHub queries (use github). Read-only — never modifies repositories.

When to use

• Triaging or ranking issues in a repository
• Identifying quick wins for contributors
• Filtering out non-actionable items (questions, duplicates)
• Detecting over-engineered proposals
• Matching issues to contributor skill levels

When not to use

• Managing forks or syncing with upstream → use `fork-manager` instead
• General GitHub CLI queries (PR status, CI runs) → use `github` instead
• Reviewing code changes before publishing → use `pr-review` instead

Skill page

Source