issue-intelligence-analyst

Cluster GitHub issues into recurring themes with counts and trend signals.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill issue-intelligence-analyst-andreicr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-intelligence-analyst
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/issue-intelligence-analyst
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill issue-intelligence-analyst-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue data often contains noise and duplicates. This Skill helps teams extract recurring themes and systemic pain signals from open and recently closed issues, enabling smarter prioritization and ideation at the product and engineering levels.

Core Features & Use Cases

  • Cluster issues by root cause and systemic patterns rather than individual tickets.
  • Detect recurrence signals by contrasting open and recently closed issues to separate solved problems from persistent pain.
  • Deliver actionable leadership-ready intelligence: concise theme descriptions, impact signals, trend indicators, and representative issues for context.
  • Use cases include understanding bug landscapes, informing roadmaps, and guiding investment decisions.

Quick Start

Provide the repository context and request an issue landscape analysis to surface themes and strategic insights.

Frequently Asked Questions about issue-intelligence-analyst

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

FAQPage Schema
How do I identify recurring themes from GitHub issues?

You can identify recurring themes from GitHub issues by analyzing open and recently closed tickets to cluster root causes. This extracts systemic pain signals, delivering theme counts, trend indicators, and representative issues for actionable context.

What is the best way to analyze bug patterns across GitHub repositories?

Analyzing bug patterns is best done by contrasting open and recently closed issues to detect recurrence signals. This cross-repository analysis separates solved problems from persistent pain, surfacing systemic patterns rather than individual tickets.

Can I extract product insights from user-reported GitHub issues?

Yes, you can extract product insights from user-reported GitHub issues by summarizing pain points into leadership-ready intelligence. This includes concise theme descriptions, impact signals, and trend indicators to inform roadmaps and guide investment decisions.

Does this issue analysis approach work with both open and closed tickets?

Yes, this issue analysis approach handles both open and recently closed tickets. Contrasting them allows you to detect recurrence signals, effectively separating problems that have already been solved from persistent systemic pain.

How do I surface systemic pain signals from a noisy GitHub issue backlog?

To surface systemic pain signals from a noisy GitHub issue backlog, you cluster issues by root cause rather than individual tickets. This filters duplicates and noise, producing actionable theme clusters with impact signals and trend analysis.