find-critical-issues

Triage GitHub issues and generate a JSON summary of critical ones.

1|2|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/chagong/IssueLens --skill find-critical-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-critical-issues
Source: https://github.com/chagong/IssueLens/tree/main/.github/skills/find-critical-issues
Command: npx skills add https://github.com/chagong/IssueLens --skill find-critical-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of triaging GitHub issues, helping to quickly identify and prioritize critical problems that require immediate attention.

Core Features & Use Cases

  • Automated Triage: Filters issues based on predefined criteria for "hot," "blocking," and "regression" issues.
  • Report Generation: Creates a structured JSON summary of identified critical issues.
  • Use Case: Automatically run this skill daily to get a report of all new critical issues that need immediate developer focus.

Quick Start

Triage issues for the past week and identify critical ones.

Frequently Asked Questions about find-critical-issues

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

FAQPage Schema
How do I triage GitHub issues to identify critical bugs automatically?

You can triage GitHub issues by analyzing them within a specified time scope and applying predefined criteria for hot, blocking, and regression issues to generate a structured JSON summary of critical bugs.

What is the best way to filter blocking and regression issues on GitHub?

Filtering blocking and regression issues involves evaluating user impact and severity within a given time scope, then producing a JSON report that details the critical issues, their summaries, and applied labels.

Can I use this to get a daily report of new critical GitHub issues?

Yes, you can run this triage process daily to analyze issues from the past day, identify critical ones based on user impact and severity, and output a JSON summary of issues requiring immediate developer focus.

What criteria are used to classify hot and blocking issues during triage?

The triage process classifies hot and blocking issues by evaluating user impact and severity, analyzing issue labels and summaries to determine which critical problems require immediate attention.

Does the triage output include all processed issues or only the critical ones?

The output includes a JSON summary detailing the identified critical issues, their summaries, and labels, along with a separate list containing all issues processed during the specified time scope.

How do I specify the time scope for analyzing recent GitHub issues?

You specify the time scope when initiating the triage process to filter issues from that period, allowing you to analyze recent GitHub issues and identify critical problems within that exact timeframe.