rank-deferred-reviews

Rank open GitHub issues labeled deferred-review against a milestone goal.

11|2|Updated Sep 8, 2015
One-click install
npx skills add https://github.com/jitrapon/astro-mobile --skill rank-deferred-reviews
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rank-deferred-reviews
Source: https://github.com/jitrapon/astro-mobile/tree/main/.claude/skills/rank-deferred-reviews
Command: npx skills add https://github.com/jitrapon/astro-mobile --skill rank-deferred-reviews

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a noisy backlog of deferred GitHub review issues into a clear, milestone-aware ranking so teams can focus on what matters most next.

Core Features & Use Cases

  • Milestone-aware triage: Compares each open deferred-review issue against a specific goal or a fallback planning document.
  • Severity and urgency scoring: Evaluates how serious each issue is and how directly it affects the current milestone.
  • Actionable output: Produces a ranked snapshot with cross-references, file areas, and recommended next actions for follow-up work.

Quick Start

Use the rank-deferred-reviews skill to rank all open deferred-review issues against the current milestone and write the results to .claude/DEFERRED_REVIEW_ISSUES.md.

Frequently Asked Questions about rank-deferred-reviews

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

FAQPage Schema
How do I rank deferred GitHub issues by milestone impact?

To rank deferred GitHub issues, compare each open deferred-review issue against a specific milestone goal or planning document to evaluate severity and urgency, generating a milestone-aware ranked snapshot for backlog triage.

What is the best way to triage a backlog of deferred-review issues against a current plan?

Triage deferred-review backlogs by scoring issue severity and urgency relative to a specific milestone goal or current-plan.md fallback, producing an actionable cross-referenced ranking to prioritize follow-up work.

Do I need GitHub CLI access to rank deferred issues by milestone?

Yes, ranking deferred issues by milestone impact requires GitHub CLI access to retrieve issue metadata and perform cross-reference analysis needed for accurate severity and urgency scoring.

How does milestone-aware scoring work for deferred-review issue triage?

Milestone-aware scoring evaluates issue severity and how directly it affects the current milestone, comparing open deferred-review issues against a specific goal or planning document to determine priority.

Where does the ranked deferred-review issue snapshot get saved?

The ranked deferred-review issue snapshot is written to a writable .claude/DEFERRED_REVIEW_ISSUES.md file, containing cross-references, file areas, and recommended next actions for follow-up work.