review-issues-severity

Prioritize open GitHub issues by severity, community impact, and maintainer abandonment.

5.8k|594|Updated Jan 26, 2022
One-click install
npx skills add https://github.com/dlt-hub/dlt --skill review-issues-severity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-issues-severity
Source: https://github.com/dlt-hub/dlt/tree/main/.claude/skills/review-issues-severity
Command: npx skills add https://github.com/dlt-hub/dlt --skill review-issues-severity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open-source maintainers and contributors struggle to identify which open GitHub issues deserve attention first, especially when serious bugs hide among hundreds of low-priority reports and maintainer responses have gone stale.

Core Features & Use Cases

  • Parallel issue discovery: Queries the GitHub API for high-comment issues, label-filtered issues, and stale issues with prior maintainer engagement.
  • Severity classification: Scores issues against signals like data corruption, long discussions, maintainer abandonment, and community reproduction effort.
  • Priority tiers and reporting: Assigns P0-P3 priorities and outputs per-issue analysis, a summary matrix, and cross-cutting pattern detection.
  • Use Case: A maintainer of the dlt repository runs a broad review to surface silently corrupting bugs that were mislabeled as questions and abandoned for months, then triages them into a P0 fix list.

Quick Start

Review the open issues in dlt-hub/dlt and prioritize them by severity, focusing on bug-labeled issues with long discussions.

Frequently Asked Questions about review-issues-severity

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

FAQPage Schema
How do I prioritize open GitHub issues by severity?

Query the GitHub API for issues sorted by comment count and staleness, then classify each against signals like data corruption, crashes, maintainer abandonment, and community reproduction effort. Assign P0-P3 tiers based on production impact and unresolved reporter investment.

How to find abandoned GitHub issues with maintainer comments?

Fetch issues with gh api sorted by update date, then inspect comment timelines with gh issue view to find cases where the last maintainer response is over two months old with no linked PR. Reporter follow-ups left unanswered are a strong abandonment signal.

Can I filter the issue review by labels or focus areas?

Yes, the skill accepts optional arguments such as label filters like bug or question, and focus areas like a specific destination or feature. Without filters it performs a broad review across all open issues in the repository.

What tools are required to run a GitHub issue severity review?

The workflow relies on the GitHub CLI (gh) with authenticated access to the target repository. It uses gh api for bulk queries with jq filtering and gh issue view for detailed per-issue analysis.

Why are question-labeled issues included in severity reviews?

Issues labeled question often represent real bugs that were initially miscategorized by maintainers or reporters. Re-examining them can surface serious problems like silent data loss that never received a proper fix.