issue-rank

Rank GitHub issues by priority labels, specificity, architectural impact, and testability.

Updated Apr 17, 2026

Search Tags:#architecture #github #testability #prioritization #triage #labels #issue-ranking

Ready to run

npx skills add https://github.com/smallorbit/smallorbit-plugins --skill issue-rank

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-rank
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/swarmkit/skills/issue-rank
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill issue-rank

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a canonical ranking framework to prioritize GitHub issues by priority labels, specificity, architectural impact, and testability, helping teams triage and schedule work more efficiently.

Core Features & Use Cases

Rank issues based on labels like priority:high, priority:medium, and other contextual notes.
Assess architectural impact and testability to surface high-value work for planning.
Use Case: When triaging a backlog, apply the ranking to surface top priorities for the next sprint and release.

Quick Start

Rank the current backlog issues by priority labels and architectural impact to produce a prioritized list.

Frequently Asked Questions about issue-rank

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prioritize GitHub issues for sprint planning and backlog grooming?▼

Prioritize GitHub issues by applying a canonical ranking framework that evaluates priority labels, specificity, architectural impact, and testability to produce a deterministic, prioritized list for triage.

What is the best way to rank GitHub issues by architectural impact and testability?▼

The best way to rank GitHub issues is to use a triage framework that scores issues based on priority labels alongside architectural impact and testability, ensuring deterministic ordering for release scheduling.

Can I use priority labels to automate issue triage across multiple GitHub repositories?▼

Yes, you can automate issue triage across repositories by integrating a ranking framework that reads priority labels like priority:high and priority:medium to drive deterministic prioritization workflows.

Does issue ranking work with existing GitHub labels like priority:high and priority:medium?▼

Issue ranking works directly with existing GitHub labels by reading priority:high, priority:medium, and other contextual notes to assess specificity and calculate a canonical priority score.

Why does my GitHub backlog triage lack deterministic ordering during sprint planning?▼

Backlog triage lacks deterministic ordering when it does not apply a canonical ranking framework that systematically weighs priority labels, architectural impact, and testability to sequence issues.

What criteria should I use to rank GitHub issues for triage decisions?▼

You should rank GitHub issues using criteria that include priority labels, issue specificity, architectural impact, and testability, ensuring a deterministic order for effective backlog grooming and triage.