analyze-issues

Analyze open GitHub issues for duplicates, tracker matches, missing labels, and supersession candidates.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/rjskene/pipeline --skill analyze-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-issues
Source: https://github.com/rjskene/pipeline/tree/main/skills/analyze-issues
Command: npx skills add https://github.com/rjskene/pipeline --skill analyze-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps GitHub issue triage by surfacing likely duplicates, tracker fits, missing required labels, and issues that may already be superseded by recent merged work—without changing anything.

Core Features & Use Cases

  • Read-only issue hygiene: Produces a digest of duplication candidates, tracker matches, label gaps, and supersession candidates for the open-issue set.
  • Deterministic shortlist + LLM confirmation: Uses a shell helper to generate candidate JSON, then dispatches an LLM subagent to confirm/deny where needed and craft suggested manual gh commands.
  • No mutations / safe decision support: Avoids automatically editing labels, closing issues, or posting comments; the user reviews the suggested actions.

Quick Start

Run /pipeline:analyze-issues to get a set of markdown tables showing duplicates, tracker fits, missing labels, and possibly superseded issues for your open issues.

Frequently Asked Questions about analyze-issues

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

FAQPage Schema
How do I find duplicate GitHub issues in my repository?

To find duplicate GitHub issues, this Skill analyzes your open issue set using a deterministic shortlist script and LLM subagent classification to identify likely duplicates. It outputs markdown tables showing duplication candidates without modifying any issues.

What is the best way to triage missing labels on GitHub issues?

The best way to triage missing labels is to run this Skill, which scans open GitHub issues for label gaps and produces a digest of missing required labels. It provides suggested manual gh commands for safe decision support without automatically editing labels.

Can I detect superseded GitHub issues after a merge without closing them automatically?

Yes, you can detect superseded GitHub issues safely. This Skill identifies issues that may already be superseded by recent merged work and generates a read-only report, ensuring zero mutations while suggesting manual gh commands for closures.

Does GitHub issue triage require write permissions to suggest label changes?

No, GitHub issue triage does not require write permissions here. This Skill operates with read-only access to provide safe decision support, generating markdown tables with suggested label edits and closures while performing zero mutations.

How do I generate a triage report for open GitHub issues?

To generate a triage report for open GitHub issues, run the analyze-issues pipeline. It uses a shell helper to generate candidate JSON and an LLM subagent to confirm verdicts, outputting markdown tables for duplicates, tracker fits, and missing labels.

Why should I avoid automatic label edits during GitHub issue triage?

You should avoid automatic label edits during GitHub issue triage to ensure change safety. This Skill provides read-only decision support by identifying label gaps and duplicates, outputting suggested manual gh commands instead of mutating issues directly.