GitHub Issues

Identify new open GitHub issues across configured repositories and rank them by urgency.

Updated Jun 3, 2026

Search Tags:#automation #github #issues #triage #digest #prioritize

Ready to run

npx skills add https://github.com/swarm-ai-research/aeon --skill github-issues-swarm-ai-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: GitHub Issues
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/github-issues
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill github-issues-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps software teams keep on top of new open GitHub issues across multiple repositories by generating a prioritized, digest-style summary.

Core Features & Use Cases

Automated triage: aggregates new open issues across repos, ranks by urgency using labels and metadata, and surfaces the most relevant items.
Daily digest: delivers a concise list suitable for quick triage notifications to engineers or managers.
Use Case: Imagine monitoring a multi-repo project; you get a daily digest of P0/P1 issues to act on first.

Quick Start

Generate today’s prioritized GitHub issues digest for your configured repositories.

Frequently Asked Questions about GitHub Issues

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

FAQPage Schema

How do I get a daily prioritized digest of new open GitHub issues?▼

To get a prioritized GitHub issues digest, this skill aggregates new open issues across configured repositories, ranks them by urgency using labels and metadata, and returns a compact, priority-ordered list for daily triage.

What is the best way to automate GitHub issue triage for multiple repositories?▼

Automating GitHub issue triage for multiple repositories is best handled by applying a 24-hour window to surface recent items, deduplicating against memory logs, and ranking issues by urgency and relevance for quick review.

How does the 24-hour window work when monitoring new GitHub issues?▼

The 24-hour window scopes the monitoring process to focus strictly on recent items, ensuring the GitHub issues digest only surfaces newly opened tickets from the last day while deduplicating previously logged entries.

Can I use GitHub labels to prioritize issues in an automated digest?▼

Yes, you can use GitHub labels to prioritize issues; the digest ranks new open tickets by urgency and relevance using label metadata to determine which P0 or P1 items require immediate action.

What information is included in a prioritized GitHub issues digest?▼

A prioritized GitHub issues digest includes the repository name, issue number, title, author, labels, and URL, returning a compact, priority-ordered list suitable for quick triage notifications.

Why am I seeing duplicate issues in my automated GitHub triage summary?▼

Duplicate issues in a GitHub triage summary appear when deduplication against memory logs fails; this skill specifically prevents duplicates by checking recent items against historical logs before generating the digest.