daily-issue-triage

Generates a daily maintainer report from open GitHub issues using a cursor-based workflow.

1.2k|95|Updated Aug 23, 2025
One-click install
npx skills add https://github.com/aizhimou/pigeon-pod --skill daily-issue-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-issue-triage
Source: https://github.com/aizhimou/pigeon-pod/tree/main/.agent/skills/daily-issue-triage
Command: npx skills add https://github.com/aizhimou/pigeon-pod --skill daily-issue-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually reviewing open GitHub issues for PigeonPod and compiling a daily maintainer report is time-consuming and error-prone. This skill automates the daily triage workflow, generating a structured report and guiding follow-up actions according to a defined rubric.

Core Features & Use Cases

  • Incremental selection of issues using the repository’s issue cursor to focus on new or updated items.
  • Classifies issues into requirement, bug, or discussion and drafts maintainer-facing analysis or applies approved follow-ups.
  • Generates and updates the daily report, and supports transitions between report and execute modes.

Quick Start

Run the daily issue triage in report mode to generate today's maintainer report from the current open issues.

Frequently Asked Questions about daily-issue-triage

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

FAQPage Schema
How do I automate daily GitHub issue triage and generate a maintainer report?

You can automate daily GitHub issue triage by running this Skill in report mode to classify open issues as requirements, bugs, or discussions and generate a structured maintainer-facing analysis.

What is the best way to classify open GitHub issues into bugs, requirements, and discussions?

The best way to classify open GitHub issues is using a decision rubric that categorizes them into requirement, bug, or discussion, then drafts maintainer-facing analysis for daily review.

How does incremental issue triage work with a repository cursor?

Incremental issue triage works by reading and updating an issue cursor in CURSOR.md to process only new or updated items, avoiding redundant reviews of previously triaged issues.

Can I execute approved follow-up actions directly from a daily issue report?

Yes, you can execute approved follow-up actions by switching from report mode to execute mode, allowing the workflow to apply decisions directly from the generated daily report.

Do I need any external dependencies to run this daily issue triage workflow?

No external dependencies are required to run this daily issue triage workflow, as it operates self-contained using internal references, CURSOR.md, and generated daily reports.

When should I switch between report and execute modes for issue triage?

You should switch between report and execute modes after reviewing the generated maintainer analysis, using execute mode to apply approved follow-up actions from the daily report.